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 B

[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] **

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 behav

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 >

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

[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, whi

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

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

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"). >

[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 ✓ - caulifl

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

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] [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

[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 pr

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

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

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 wri

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