I type M-x org-agenda in org-mode, the list of commands shows, I press a, the agenda buffer opens but only shows the dates, and pressing L won't expand:-
Week-agenda (W27):
Monday 1 July 2019 W27
Tuesday 2 July 2019
Wednesday 3 July 2019
Thursday 4 July 2019
Friday 5 July 2019
Saturday 6 July 2019
Sunday 7 July 2019
================================================================
Global list of TODO items of type: ALL
I am seeing the same problem with emacs 24, 25, 26 on Win 7. The same file shows detailed timelines fine on a debian machine.
As reported in a now deleted comment, timeline view is no more (org-mode version 9.1 onwards). See https://www.orgmode.org/Changes_old.html
Related
The following cron expression:
0 3 1 5-5/3 *
“At 03:00 on day-of-month 1 in every 3rd month from May through May.”
Is not accepted by Github actions:
on:
schedule:
- cron: "0 3 1 5-5/3 *" ## Day 1, every 3rd month May-May
With the following output:
ERROR: String does not match the pattern of "^(((\d+,)+\d+|((\d+|\*)/\d+|((JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC)(-(JAN|FEB|MAR|APR|MAY|JUN|JUL|AUG|SEP|OCT|NOV|DEC))?))|(\d+-\d+)|\d+|\*|((MON|TUE|WED|THU|FRI|SAT|SUN)(-(MON|TUE|WED|THU|FRI|SAT|SUN))?)) ?){5}$".yaml-schema: GitHub Workflow
How is it possible to run a cron starting 1st of May, every 3 months, until the next May?
Your cron expression probably does not what you expect. The part 5-5/3 restricts the execution times to May only. This results in a job that will be run at 03:00 on the first day of every May:
2022-05-01 03:00:00
2023-05-01 03:00:00
2024-05-01 03:00:00
The regex that GitHub is using to verify the cron expression (according to the error message in your question) does not allow defining a range and step at the same time. This might be a bug as such expressions would usually be valid.
To fix this, you could list all months in the cron expression directly like 0 3 1 5,8,11,2 * which results in the following schedule:
2022-05-01 03:00:00
2022-08-01 03:00:00
2022-11-01 03:00:00
2023-02-01 03:00:00
2023-05-01 03:00:00
2023-08-01 03:00:00
2023-11-01 03:00:00
2024-02-01 03:00:00
For emacs25 (emacs 25.2.2 on ubuntu 17.10), I am not able to get org-agenda-list working. org-timeline shows me details on a daily basis, but org-agenda-list just lists the names of the days and there are no details listed.
I have the following .emacs (simplified down to one line to track down why org-agenda is not working - I know emacs reasonably well, but I am a first time user of org-mode)
(global-set-key "\C-ca" 'org-agenda)
and with an empty .emacs.d directory, when I run org-agenda-list for the following example:
* Tasks
** DONE [#A] do this y'day
SCHEDULED: <2018-03-22 Thu>
** TODO [#A] do this tomorrow
SCHEDULED: <2018-03-24 Sat>
** TODO [#A] this task is not scheduled
** TODO [#B] scheduled for today, priority B
SCHEDULED: <2018-03-23 Fri>
** IN PROGRESS [#A] scheduled today and deadline in 2 days
DEADLINE: <2018-03-25 Sun> SCHEDULED: <2018-03-23 Fri>
** TODO [#A] deadline in 2 days and not scheduled
DEADLINE: <2018-03-25 Sun>
** TODO [#A] scheduled for monday
SCHEDULED: <2018-03-29 Thu>
** TODO [#C] do this today if I get time
SCHEDULED: <2018-03-23 Fri>
** TODO [#B] neither is this one
** TODO [#C] or this one
** TODO [#A] deadline in 10 days and not scheduled
DEADLINE: <2018-03-31 Sat>
I only see the week entries and it is missing all the details for the daily tasks
Week-agenda (W12):
Monday 19 March 2018 W12
Tuesday 20 March 2018
Wednesday 21 March 2018
Thursday 22 March 2018
Friday 23 March 2018
Saturday 24 March 2018
Sunday 25 March 2018
Where as org-timeline shows me the details for the daily tasks
Thursday 22 March 2018
Scheduled: DONE [#A] do this y'day
-------------------------------------------------------------------------------
Friday 23 March 2018
Scheduled: IN PROGRESS [#A] scheduled today and deadline in 2 days
Scheduled: TODO [#B] scheduled for today, priority B
Scheduled: TODO [#C] do this today if I get time
Saturday 24 March 2018
Scheduled: TODO [#A] do this tomorrow
Sunday 25 March 2018
Deadline: IN PROGRESS [#A] scheduled today and deadline in 2 days
Deadline: TODO [#A] deadline in 2 days and not scheduled
[... 4 empty days omitted]
Thursday 29 March 2018
Scheduled: TODO [#A] scheduled for monday
Friday 30 March 2018
Saturday 31 March 2018
Deadline: TODO [#A] deadline in 10 days and not scheduled
Q: How do I get org-agenda-list to work properly for me ?
Moreover after I installed
M-x package-install org-edna
based on some online advice, I also lost the org-timeline command, which I recovered via brute-force application of "apt remove emacs" and "apt install emacs".
Q: Can anyone explain to me why I had lost the org-timeline command ?
Thanks.
Check : C-h v org-agenda-files. If your file is not there then, while your file is opened in the buffer, use M-x org-agenda-file-to-front. Now try M-x org-agenda. You can check C-h v org-agenda-files again and you will find your file there.
I try to convert the character "Friday, March 24, 2017 4:39:46 PM" into a date, but it does not work. dat.1 results in NA. Can anyone tell me, how to fix it.
dat <- c("Friday, March 24, 2017 4:39:46 PM")
dat.1 <- strptime(dat, format="%A, %B %d, %Y %I:%M:%S %p")
dat.1
Result
[1] NA
EDIT. K..pradeeep pointed out that the code is running on his pc. On my it does not work. I use a Macbook Air, OS X 10.12.3. Version:
platform x86_64-apple-darwin15.6.0
arch x86_64
os darwin15.6.0
system x86_64, darwin15.6.0
status
major 3
minor 4.0
year 2017
month 04
day 21
svn rev 72570
language R
version.string R version 3.4.0 (2017-04-21)
nickname You Stupid Darkness
I followed this guide to implementing build numbers in an XCode iPhone project (guide).
I tried it and I am getting the wrong build number when NSLogging. It's not updating correctly and is always one or two numbers behind the info.plist. I need it to be the same number. Anyone know why this is happening?
i.e "[[[NSBundle mainBundle] infoDictionary] objectForKey:#"CFBuildNumber"]" is not the same as the plist's CFBuildNumber.
The script is set to run first, before copy bundle resources and everything. This is the output and info.plist numbers I get:
Application Version: 1.0 Build No: 52 Build Date: Wed Nov 10 15:10:05 CET 2010
(info.plist is build number: 54 and date: Wed Nov 10 15:10:43 CET 2010)
Application Version: 1.0 Build No: 54 Build Date: Wed Nov 10 15:10:43 CET 2010
(info.plist is build number: 55 and date: Wed Nov 10 15:12:54 CET 2010)
Application Version: 1.0 Build No: 54 Build Date: Wed Nov 10 15:10:43 CET 2010
(info.plist is build number: 56 and date: Wed Nov 10 15:13:49 CET 2010)
Application Version: 1.0 Build No: 56 Build Date: Wed Nov 10 15:13:49 CET 2010
(info.plist is build number: 57 and date:Wed Nov 10 15:14:46 CET 2010)
It seems to follow this pattern throughout. So continuing it would be 56 (real 58), 58 (real 59), 58 (real 60), 60 (real 61), 60 real (62), 62 (real 63) etc. etc.
The script (that is set to run before everything else) is:
#!/bin/bash
# Auto Increment Version Script
buildPlist="Project-Info.plist"
CFBuildNumber=$(/usr/libexec/PlistBuddy -c "Print CFBuildNumber" $buildPlist)
CFBuildNumber=$(($CFBuildNumber + 1))
/usr/libexec/PlistBuddy -c "Set :CFBuildNumber $CFBuildNumber" $buildPlist
CFBuildDate=$(date)
/usr/libexec/PlistBuddy -c "Set :CFBuildDate $CFBuildDate" $buildPlist
Because project's Info.plist processed prior to 'Run Script' phase. See 'Build results' window in XCode. To resolve this you should
1) Create new target with type "Run script only" and configure it to update version number
2) Create new target with type "Aggregate" and add to it "Version update" target and "you product" target.
So when you build "Aggregate" target, at first step - version will be updated, and at second step - your product.
I ended up using the already-copied plist file, ${TARGET_BUILD_DIR}/${INFOPLIST_PATH}, and placing the "copy bundle resources"-phase before the script runs instead. That way the number will always be synchronized.
I recently stumbled upon a cool feature in CVS where you can name revisions by date, e.g.:
# List changes made between the latest revision 24 hours ago and now
cvs diff -D "1 day ago"
Do any other repository systems (e.g. Git, SVN, Bazaar, Mercurial, etc.) have an option like this?
Subversion has a similar feature. For example:
svn diff -r {2010-07-31}
The syntax is explained in http://svnbook.red-bean.com/en/1.5/svn.tour.revs.specifiers.html#svn.tour.revs.dates
Mercurial has a wide range of date formats: http://www.selenic.com/mercurial/hg.1.html#date-formats, though maybe not "1 day ago".
This subversion bug report indicates that Subversion can't do it natively, but does offer a tip on using date to do it:
(2) Whilst Subversion doesn't understand -r "{3 days ago}", date can
help out there too: -r "{date -Is -d '3 days ago'}".
(answering my own question)
git log supports dates for filtering before or after given times. Example:
git log --after='july 17 2010' --before='july 31 2010'
Here's a shell script that makes it a little easier to list ranges of commits, but it also uses a terser format than git log's default:
#!/bin/sh
# git-changes
FORMAT='%cd%x09%h%n%x09%s%n'
CMD="git log --format=format:$FORMAT"
case $# in
0 )
$CMD ;;
1 )
$CMD "--after=`date -d "$1"`" ;;
2 )
$CMD "--after=`date -d "$1"`" --before="`date -d "$2"`";;
esac
Note: I wrapped the date arguments with the date command, since git treats 'July 17' as a few hours off from 'July 17 2010' for some reason.
Usage:
git-changes # Same as git log, but more terse
git-changes 'yesterday' # List all commits from 24 hours ago to now
git-changes 'jul 17' 'aug 1' # List all commits after July 17 at midnight
# and before August 1 at midnight.
Sample output of git-changes 'jul 17' 'aug 1':
Sat Jul 31 23:43:47 2010 -0400 86a6727
* Moved libcurl into project directory as static lib.
Sat Jul 31 20:04:24 2010 -0400 3a4eb10
* Added configuration file support.
Sat Jul 31 17:44:53 2010 -0400 aa2046b
* Fixed truncation bug in bit parser.
Sat Jul 17 00:10:57 2010 -0400 99e8124
* Added support for more bits.
Now, to see all changes introduced by commit 99e8124, type git show 99e8124. To see all changes since revision 99e8124 (not including that commit itself), type git diff 99e8124.