git-annex/doc/git-annex-rmurl.mdwn

# NAME

git-annex rmurl - record file is not available at url

# SYNOPSIS

git annex rmurl `[file url ..]`

# DESCRIPTION

Record that the file is no longer available at the url.

Removing the last web url will make git-annex no longer treat content as being
present in the web special remote. If some other special remote
claims the url, unregistering the url will not update presence information
for it, because the content may still be present on the remote.

# OPTIONS

* `--batch`

  Enables batch mode, in which lines are read from stdin.
  Each line should contain the file, and the url to remove from that file,
  separated by a single space.

* `-z`

  Makes the `--batch` input be delimited by nulls instead of the usual
  newlines.

* Also the [[git-annex-common-options]](1) can be used.

# SEE ALSO

[[git-annex]](1)

[[git-annex-addurl]](1)

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# NAME`

			`git-annex rmurl - record file is not available at url`

			`# SYNOPSIS`

rmurl: --batch * rmurl: Multiple pairs of files and urls can be provided on the command line. * rmurl: Added --batch mode. This commit was sponsored by Trenton Cronholm on Patreon. 2016-12-05 16:10:07 +00:00			git annex rmurl `[file url ..]`
splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00
			`# DESCRIPTION`

			`Record that the file is no longer available at the url.`

clarify 2021-03-22 16:15:54 +00:00			`Removing the last web url will make git-annex no longer treat content as being`
restore old registerurl location tracking behavior registerurl: When an url is claimed by a special remote other than the web, update location tracking for that special remote. registerurl's behavior was changed in commit 451171b7c1eaccfd0f39d4ec1d64c6964613f55a, apparently accidentially to not update location tracking except for the web. This makes registerurl followed by unregisterurl not be a no-op, when the url happens to be claimed by a remote other than the web. It is a noop when the url is unclaimed except by the web. I don't like the inconsistency, and wish that registerurl and unregisterurl never updated location tracking, which would be more in keeping with them being plumbing. But there is the fact that it used to behave this way, and also it was inconsistent that it updated location tracking for the web but not for other remotes, unlike addurl. And there's an argument that the user might not know what remote to expect to claim an url, so would be considerably in the dark when using registerurl. (Although they have to know what content gets downloaded, since they specify a key..) Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project 2023-04-05 20:59:44 +00:00			`present in the web special remote. If some other special remote`
			`claims the url, unregistering the url will not update presence information`
			`for it, because the content may still be present on the remote.`
mention location tracking 2018-10-04 21:37:20 +00:00
rmurl: --batch * rmurl: Multiple pairs of files and urls can be provided on the command line. * rmurl: Added --batch mode. This commit was sponsored by Trenton Cronholm on Patreon. 2016-12-05 16:10:07 +00:00			`# OPTIONS`

			* `--batch`

			`Enables batch mode, in which lines are read from stdin.`
			`Each line should contain the file, and the url to remove from that file,`
			`separated by a single space.`

added -z Added -z option to git-annex commands that use --batch, useful for supporting filenames containing newlines. It only controls input to --batch, the output will still be line delimited unless --json or etc is used to get some other output. While git often makes -z affect both input and output, I don't like trying them together, and making it affect output would have been a significant complication, and also git-annex output is generally not intended to be machine parsed, unless using --json or a format option. Commands that take pairs like "file key" still separate them with a space in --batch mode. All such commands take care to support filenames with spaces when parsing that, so there was no need to change it, and it would have needed significant changes to the batch machinery to separate tose with a null. To make fromkey and registerurl support -z, I had to give them a --batch option. The implicit batch mode they enter when not provided with input parameters does not support -z as that would have complicated option parsing. Seemed better to move these toward using the same --batch as everything else, though the implicit batch mode can still be used. This commit was sponsored by Ole-Morten Duesund on Patreon. 2018-09-20 20:09:21 +00:00			* `-z`

			Makes the `--batch` input be delimited by nulls instead of the usual
			`newlines.`

split out common options to its own page and mention it on each subcommand page Sometimes users would get confused because an option they were looking for was not mentioned on a subcommand's man page, and they had not noticed that the main git-annex man page had a list of common options. This change lets each subcommand mention the common options, similarly to how the matching options are handled. This commit was sponsored by Svenne Krap on Patreon. 2021-05-10 19:00:13 +00:00			`* Also the [[git-annex-common-options]](1) can be used.`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# SEE ALSO`

			`[[git-annex]](1)`

expand manpages cross-references significantly i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well. 2015-05-29 16:12:55 +00:00			`[[git-annex-addurl]](1)`

splitting up the man page Common command man pages all split out and often expanded. A few sections split out into their own pages. Still need to do all the other commands.. 2015-03-23 19:36:10 +00:00			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

			`Warning: Automatically converted into a man page by mdwn2man. Edit with care.`