Re: [O] List unstuck projects in agenda
Hi Adam, > You may find org-ql helpful, as it makes selecting entries easy and > flexible. > > https://github.com/alphapapa/org-ql > > Here's an example that might help: > > https://github.com/alphapapa/org-ql/blob/master/examples.org#stuck-projects-block-agenda Thanks for the suggestion. I was hoping to stick with stock orgmode. Nonetheless, I gave it a try. It couldn't quite make it meet my desires (I put some more info in GitHub issues), but overall it looks neat. Josiah
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
maybe add org-lint to the after-save-hook - maybe something like (untested) (add-hook 'after-save-hook (lamda () (when (eq buffer-mode 'org-mode) (org-lint Christoph Groth writes: > Nicolas Goaziou wrote: >> Christoph Groth writes: >> >> > I understand now that Org does what it should. However, I find this >> > behavior quite dangerous. It caught me after more than 10 years of >> > using Org. If there's a list of long-term issues with Org >> > somewhere, this problem may deserve being added to it. >> >> I don't think there is much to fix here. In any case, the command >> `org-lint' warns you about this kind of error. > > Thanks for mentioning 'org-lint'. I just ran it on my agenda files, and > it found multiple errors in most of my (very long) files. So at least > for me (and likely for other Org users as well), the risk of missing > TODO items is real - that's a rather serious problem for a task manager! > > My agenda files are populated using 'org-capture'. Do you have > suggestions how to best integrate org-lint transparently into everyday > org usage? For example, files could be linted automatically before they > are saved, or before a new item is captured. -- Tim Cross
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
You may also find the command M-x org-lint useful. I regularly run it on my larger org files after an org release to spot problems in my org files (either due to my error or changes in orgmode) Tim Christoph Groth writes: > Nicolas Goaziou wrote: > >> Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must >> appear right after the headline, per Org syntax. This is specified at >> the first paragraph in (info "(org) Deadlines and Scheduling"). >> >> Elswhere, only the timestamp is meaningful to Org. > > Thanks for the quick clarification! I didn't see the relevant line in > the documentation since my Emacs from Debian shows only the info > documentation for the (outdated) Org that is bundled with Emacs [1]. > > I understand now that Org does what it should. However, I find this > behavior quite dangerous. It caught me after more than 10 years of > using Org. If there's a list of long-term issues with Org somewhere, > this problem may deserve being added to it. > > Cheers > Christoph > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725408 -- Tim Cross
Re: [O] List unstuck projects in agenda
Hi Josiah, You may find org-ql helpful, as it makes selecting entries easy and flexible. https://github.com/alphapapa/org-ql Here's an example that might help: https://github.com/alphapapa/org-ql/blob/master/examples.org#stuck-projects-block-agenda
[O] List unstuck projects in agenda
Hello, I want to separately display stuck and unstuck projects in my agenda. I define my stuck projects via setting org-stuck-projects, so displaying stuck ones is easy (via a (stuck "") in org-agenda-custom-commands). I want to have another section of the agenda that displays only my unstuck projects. I am finding this difficult. I searched the list archives and found this old thread. https://lists.gnu.org/archive/html/emacs-orgmode/2010-01/msg00104.html Is a something along the lines of a copy-paste-tweak of org-agenda-list-stuck-projects still the easiest way to go? Josiah
Re: [O] [Patch] Hide the file column in a clock report.
Hello, Michaël Cadilhac writes: > Here attached. Let me know if that's all good! It is. Applied. Could you provide an ORG-NEWS entry? Thank you! Regards, -- Nicolas Goaziou
Re: [O] Completely hide the :PROPERTIES: drawer in org-mode.
Hello, Michaël Cadilhac writes: > Apologies for the delay. > > Is that alright? It is. Applied. Thank you! Regards, -- Nicolas Goaziou
Re: [O] org-icalendar: Change dates to today in VEVENT export
Hello, Michaël Cadilhac writes: > Hopefully I didn't miss anything—I've been running the patched version for > weeks now, so it should be stable in any case. Patch 0003 above should > still be OK. Thank you. > +(defcustom org-icalendar-summary-uses-tags nil > + "Whether tags should be added to the title to create the summary. > + > +If a SUMMARY is provided in the entry, this is irrelevant. > +If non-nil, it can be set to `local-tags' or `all-tags' indicating which tags > +are used to make up the summary: only tags defined in the current line or all > +tags including inherited ones, respectively." > + :group 'org-export-icalendar > + :type '(choice > + (const :tag "Use the tags defined in current line" local-tags) > + (const :tag "Use all tags, including inherited ones" all-tags) > + (const :tag "Do not use tags in summary" nil))) There are missing keywords (:package-version, :safe). > +(defun org-icalendar-today-timestamp () > + "Return a TIMESTAMP object for today, at 00:00." > + (let ((dt (decode-time))) > +(list 'timestamp > + (nconc (list :year-start (nth 5 dt) > +:year-end (nth 5 dt) > +:month-start (nth 4 dt) > +:month-end (nth 4 dt) > +:day-start (nth 3 dt) > +:day-end (nth 3 dt)) This function already exists: `org-timestamp-from-time'. Could you use that instead? Othewise, LGTM. Regards, -- Nicolas Goaziou
[O] Make beamer items ticked or alerted via overlay?
Hi, When writing a beamer presentation with Org, is it possible to use an overlay to first produce a list, like - apples - beetroots - cauliflowers - damsons - eggs and then either change the colour of some subset of the items, or put a tick after each one, e.g. - apples - beetroots ✓ - cauliflowers - damsons ✓ - eggs ? Cheers, Loris -- This signature is currently under construction.
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
On Thu, Sep 5, 2019 at 3:38 PM Christoph Groth wrote: > Nicolas Goaziou wrote: > > > Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must > > appear right after the headline, per Org syntax. This is specified at > > the first paragraph in (info "(org) Deadlines and Scheduling"). > > > > Elswhere, only the timestamp is meaningful to Org. > > Thanks for the quick clarification! I didn't see the relevant line in > the documentation since my Emacs from Debian shows only the info > documentation for the (outdated) Org that is bundled with Emacs [1]. > This is, in fact, one of the very few things that did change with the introduction of org-elements.el and the fore formal parsing of Org files. Originally, SCHEDULED and DEADLINE could be anywhere in the entry. But with the development of the parser, and (I think) in order to define everything well in particular also for the export backends, the planning information was confined to the first line. I don't think you need to be worried about more surprises, this was the most significant one IIRC. Carsten > > I understand now that Org does what it should. However, I find this > behavior quite dangerous. It caught me after more than 10 years of > using Org. If there's a list of long-term issues with Org somewhere, > this problem may deserve being added to it. > > Cheers > Christoph > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725408 > >
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
Nicolas Goaziou wrote: > Christoph Groth writes: > > > I understand now that Org does what it should. However, I find this > > behavior quite dangerous. It caught me after more than 10 years of > > using Org. If there's a list of long-term issues with Org > > somewhere, this problem may deserve being added to it. > > I don't think there is much to fix here. In any case, the command > `org-lint' warns you about this kind of error. Thanks for mentioning 'org-lint'. I just ran it on my agenda files, and it found multiple errors in most of my (very long) files. So at least for me (and likely for other Org users as well), the risk of missing TODO items is real - that's a rather serious problem for a task manager! My agenda files are populated using 'org-capture'. Do you have suggestions how to best integrate org-lint transparently into everyday org usage? For example, files could be linted automatically before they are saved, or before a new item is captured.
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
Christoph Groth writes: > I understand now that Org does what it should. However, I find this > behavior quite dangerous. It caught me after more than 10 years of > using Org. If there's a list of long-term issues with Org somewhere, > this problem may deserve being added to it. I don't think there is much to fix here. In any case, the command `org-lint' warns you about this kind of error.
[O] Getting org-plus-contrib but releases only
Hi all, I have a question regarding Org installation. It is probably known, but I’m failing to find proper guidance on the matter. So, if I missed something obvious, a pointer would be kind enough. As far as I understand, there are three typical ways to “get” Org: the built-in version, which lags somewhat behind; (GNU) Elpa, the default package repository, which offers the latest released version; and Org Elpa, which we can add as a repository, and which offers weekly builds. Also, as far as I get, only Org Elpa contains 'org-plus-contrib' for installation. (Or am I missing something?) I am a user of some of the 'contrib' packages, and would like to keep that. But I currently would like some more stability here, so I’d like to get releases only for updates of Org (but the latest ones, such as GNU Elpa does). Is there a (recommended) way to do both of these things at the same time? Best regards, Gustavo Barros.
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
Nicolas Goaziou wrote: > Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must > appear right after the headline, per Org syntax. This is specified at > the first paragraph in (info "(org) Deadlines and Scheduling"). > > Elswhere, only the timestamp is meaningful to Org. Thanks for the quick clarification! I didn't see the relevant line in the documentation since my Emacs from Debian shows only the info documentation for the (outdated) Org that is bundled with Emacs [1]. I understand now that Org does what it should. However, I find this behavior quite dangerous. It caught me after more than 10 years of using Org. If there's a list of long-term issues with Org somewhere, this problem may deserve being added to it. Cheers Christoph [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725408
Re: [O] Bug: Language code for Brazilian in org-latex-babel-language-alist and org-latex-polyglossia-language-alist
Hello, Gustavo Barros writes: > I hadn’t checked the commit back then, but now I was seeing if I could > remove my local workaround on this and I noticed that while > `org-latex-babel-language-alist' is now looking good, > `org-latex-polyglossia-language-alist' was not changed. (This is so in > an up to date org-plus-contrib-20190904/ox-latex.el). Fixed, too! Thank you. Regards, -- Nicolas Goaziou
Re: [O] Bug? SCHEDULED lines treated differently when text precedes them
Hello, Christoph Groth writes: > With Org 9.2.3, the following two TODO items behave differently: > > ** TODO Something > blabla > SCHEDULED: <2019-09-01 Sun> > [2019-09-05 Thu 14:39] > ** TODO Something else > SCHEDULED: <2019-09-01 Sun> > foobar > [2019-09-05 Thu 14:40] > > The first one behaves as expected, i.e. it appears in today's > (2019-09-05) agenda, since it's not done yet. > > The second one does appear in today's agenda, but it is visible for the > day 2019-09-01. > > Is this behavior by design? If yes, could someone please explain the > rationale or point me to relevant documentation or discussions? Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must appear right after the headline, per Org syntax. This is specified at the first paragraph in (info "(org) Deadlines and Scheduling"). Elswhere, only the timestamp is meaningful to Org. Regards, -- Nicolas Goaziou
[O] Bug? SCHEDULED lines treated differently when text precedes them
Dear org mode experts, I have noticed the following behavior that (after reading the relevant documentation) I find at least surprising and error-prone. With Org 9.2.3, the following two TODO items behave differently: ** TODO Something blabla SCHEDULED: <2019-09-01 Sun> [2019-09-05 Thu 14:39] ** TODO Something else SCHEDULED: <2019-09-01 Sun> foobar [2019-09-05 Thu 14:40] The first one behaves as expected, i.e. it appears in today's (2019-09-05) agenda, since it's not done yet. The second one does appear in today's agenda, but it is visible for the day 2019-09-01. Is this behavior by design? If yes, could someone please explain the rationale or point me to relevant documentation or discussions? Thanks! Christoph
Re: [O] Bug: Language code for Brazilian in org-latex-babel-language-alist and org-latex-polyglossia-language-alist
Hi Nicolas,
On Thu, Aug 15 2019, Nicolas Goaziou wrote:
Hello,
Gustavo Barros writes:
`org-latex-babel-language-alist' and
`org-latex-polyglossia-language-alist' have the language code for
Brazilian as =("bt-br" . "brazilian")=. I am a native Brazilian and
our language is Portuguese, and Brazilian Portuguese is a variant.
That to say that I’ve never seen the language code "bt-br" to refer
to
"brazilian", whereas the usual code is "pt-br" (hyphen or
underscore).
So this looks very much like a typo.
Fixed. Thank you!
I hadn’t checked the commit back then, but now I was seeing if I could
remove my local workaround on this and I noticed that while
`org-latex-babel-language-alist' is now looking good,
`org-latex-polyglossia-language-alist' was not changed. (This is so in
an up to date org-plus-contrib-20190904/ox-latex.el).
Best regards,
Gustavo.
