-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--newer-than=SPEC #21
Comments
It is explained just below in the man page: "For option --newer-than you can either specify a file or time specification like that used by at(1) command, e.g. |
Ahhhh - yes - I am sorry. I missed that paragraph. Thanks. |
Hi now I want use Thanks |
It's fairly complex time specifications, extending the POSIX.2 standard. The definition of the time specification can be found in /usr/share/doc/at-3.1.13/timespec For your task "now-1month" should work. |
For those that find this issue later have a look at "AT(1)" online man page: |
Two years later the manual is still unclear on this point. 'SPEC' should be replaced with a distinct and easy to find meta-name such as AT_SPEC (searching in many case insensitive environments practically highlights the entire document as potential matches). In one part of the document AT_SPEC can be defined as a reference to the manual page for the at command (actually 'at' isn't installed on the system I want to use lftp on, so this could be unhelpful), but also a couple example formats should be provided. EG: 2006-01-02T15:04:05 (absolute) I don't even know if these two examples are accurate, since the webpage transcription of the manual for the at command is written in an information-dense paragraph style instead of with easy to digest examples or construction rules. |
Has anybody ever tried the "If you specify a file, then modification time of that file will be used." part ? Edit: |
hi
it would be great if the docs can be updated with information what format should the SPEC in --newer-than=SPEC be.
No info in google on that.
Thanks.
Krystian
The text was updated successfully, but these errors were encountered: