Re: [O] [RFC] Dog food, anyone?

Hello, Bastien writes: > it would be nice to make the switch to org-manual.org for Org 9.2, > and to delete org.texi entirely from the master branch. Done. > I guess we need to add some Makefile rules so that "make pdf" first > exports .org => .texi then exports .texi to .pdf...

Re: [O] Missing `Specific Header Arguments' in Manual

Hello, "Berry, Charles" writes: > @cindex @code{:sep}, src header argument > > The @code{:sep} header argument is the delimiter for saving results as tables > to files (@pxref{file}) external to Org mode. Org defaults to tab delimited > output. The function,

Re: [O] "DONE" markers have different colors?

Aloha Kaushal, Kaushal Modi writes: Hello, On Tue, May 8, 2018 at 5:56 PM Thomas S. Dye wrote: These are from two differently colored TODO cookies, not DONE cookies. There are text properties here: face (:inherit hl-todo :foreground "#cc9393")

Re: [O] "DONE" markers have different colors?

Hello, On Tue, May 8, 2018 at 5:56 PM Thomas S. Dye wrote: > > These are from two differently colored TODO cookies, not DONE > cookies. > > There are text properties here: > face (:inherit hl-todo :foreground "#cc9393") > fontifiedt >

Re: [O] "DONE" markers have different colors?

Aloha Kaushal, Kaushal Modi writes: Hello Thomas, Zongheng, On Tue, May 8, 2018 at 5:34 PM Thomas S. Dye wrote: Hi, Zongheng Yang writes: > Hi, > > Lately I've noticed that in my org-mode files, the "DONE" > markers started > showing different colors. I don't believe

Re: [O] "DONE" markers have different colors?

Hello Thomas, Zongheng, On Tue, May 8, 2018 at 5:34 PM Thomas S. Dye wrote: > Hi, > > Zongheng Yang writes: > > > Hi, > > > > Lately I've noticed that in my org-mode files, the "DONE" > > markers started > > showing different colors. I don't believe this happened before. > >

Re: [O] "DONE" markers have different colors?

Hi, Zongheng Yang writes: Hi, Lately I've noticed that in my org-mode files, the "DONE" markers started showing different colors. I don't believe this happened before. Any ideas? Is this a recent org-mode change? I see this, too. All the best, Tom -- Thomas S. Dye http://www.tsdye.com

Re: [O] "DONE" markers have different colors?

you can set kw colors. also, some monitors show colors depending on vantage.

Re: [O] "DONE" markers have different colors?

Hello, Zongheng Yang writes: > Lately I've noticed that in my org-mode files, the "DONE" markers started > showing different colors. I don't believe this happened before. Any ideas? > Is this a recent org-mode change? It doesn't ring a bell. You may want to check your

[O] "DONE" markers have different colors?

Hi, Lately I've noticed that in my org-mode files, the "DONE" markers started showing different colors. I don't believe this happened before. Any ideas? Is this a recent org-mode change? Screenshot: https://imgur.com/a/nsk22Xx I'm using org-plus-contrib-20180129.

Re: [O] Orgalist notes

Hi Nicolas, * Nicolas Goaziou [2018-05-07; 22:29]: > Gregor Zattler writes: > >> Yes, I used the customization interface and choose "2)". [This >> produces 41 as value of this variable. I did so, because >> sometimes a sentence ends in a number and a

Re: [O] Localized org-mode

ST writes: > Why? Run "detranslator" before you start parsing. I.e. based on your > 1-to-1 vocabulary "detranslator" will substitute all :EIGENSCHAFTEN: and > all other org syntax back to English :PROPERTIES: etc.. Then apply > parser as usual. You cannot blindly replace all

Re: [O] Localized org-mode

> > is there something like localized/internationalized org? I.e. all > > keywords, like :PROPERTIES: are translated to another language, > > like :EIGENSCHAFTEN: (for German) so it looks more natural in a foreign > > language. It is of a special importance for languages with non-latin > >

Re: [O] BUG: org tag can align proper when tag is Chinese.

Hello, tumashu writes: > I found [:alnum:] can match Chinese > > (string-match-p "[[:alnum:]]" "@@@你好") => 3 Great. > > But using [:word:] may better, in my opinion. I'm not so sure about it. It would be better to see a concrete limitation before extending syntax for

Re: [O] [PATCH] Add new keyword :coding for #+include directive

Hello, pierre.techouey...@free.fr (Pierre Téchoueyres) writes: > Hello Nicolas, > Did you have time to review the patches ? Sorry for the delay, I have been sidetracked. I admit I don't fully understand your bugfix patch, i.e., "[PATCH] Correctly convert encoding of included files". For the

Re: [O] Missing `Specific Header Arguments' in Manual

Bastien writes: > See line 17450 in doc/org-manual.org of the current master. This is not a section, actually not in the Texinfo sense. See line 17452 in the same document. I.e., there is no node attached to it, it cannot be accessed from "m" menu from `info', and it doesn't

Re: [O] Missing `Specific Header Arguments' in Manual

Hi Nicolas, Nicolas Goaziou writes: >> There is a section called "Header arguments" in the new >> org-manual.org. > > No, there is not. See line 17450 in doc/org-manual.org of the current master. -- Bastien

Re: [O] Localized org-mode

Hello, ST writes: > is there something like localized/internationalized org? I.e. all > keywords, like :PROPERTIES: are translated to another language, > like :EIGENSCHAFTEN: (for German) so it looks more natural in a foreign > language. It is of a special importance for

Re: [O] Missing `Specific Header Arguments' in Manual

Hello, Bastien writes: > Why did you remove colon prefixes? As I explained, many structural objects start with a colon. Some of them were indexed with a colon, others were not. This is confusing. The best solution was to remove colons from entries in index. Adding colons

Re: [O] Smooth transition for modules

Hi Bastien, 2018ko maiatzak 8an, Bastien-ek idatzi zuen: [...] > > You mean: instead of simply requiring other packages from a package, > add a new Suggest: header for packages suggestions? Everything you described sounds like a wonderful idea. What I had in mind was much simpler. It (I

[O] Localized org-mode

Hello, is there something like localized/internationalized org? I.e. all keywords, like :PROPERTIES: are translated to another language, like :EIGENSCHAFTEN: (for German) so it looks more natural in a foreign language. It is of a special importance for languages with non-latin letters, where the

Re: [O] Smooth transition for modules

Hi Aaron, thanks for your feedback. Ecay writes: > Indeed, the patch was written under that assumption. If the situation > changes, (at least) some tweaks would be needed. I will think again about the whole issue and propose a change when I have some code to show. > I

Re: [O] Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]"))

Hi Bastien, 2018ko maiatzak 8an, Bastien-ek idatzi zuen: > Thanks -- I tested it. Thanks :) > I like the idea of sending a warning to the user for > backward-incompatible changes but in this case, well, we take for > granted that org-tempo will be turned off by default in the next >

Re: [O] Bug: ob-python: Lots of IndentationError [9.1.12 (release_9.1.12-728-ge8a4f3 @ /Users/xcy/src/org-mode/lisp/)]

Hi, Xu Chunyang writes: > By the way, the implementation of ob-python.el is not very robust. Yes, we need help for this. -- Bastien

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Nicolas, Nicolas Goaziou writes: > It seems nonsensical to let Org handle expansion templates. Not to me, because Org syntax include default structured templates. > Dedicated packages do it way better than what we provide, and the > task is really out of our scope.

Re: [O] Missing `Specific Header Arguments' in Manual

Hi Nicolas, Nicolas Goaziou writes: > Kaushal Modi writes: > >> In the Org 9.1 version manual, it was possible to search ":eval" and find >> what I was looking for. In 9.2 manual, very few of the header arguments are >> documented with the colon

Re: [O] Tag completion does not work well with org-complete-tags-always-offer-all-agenda-tags

Hi Alain, alain.coch...@unistra.fr writes: > With variable org-complete-tags-always-offer-all-agenda-tags set to > true, tag completion does not work as I expect. Specifically, upon > 'C-c C-q' or 'C-c C-c', it works fine if I enter in the minibuffer > some letter and then press , but not if I

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Rasmus, Rasmus writes: > Do you think org-tempo should try to detect "old" versions of > org-structure-template-alist and give a better error if it sees one? Yes, it definitely should detect old format and fix it. -- Bastien

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Aaron, Aaron Ecay writes: > Not AFAIK (to both questions). Yasnippet is in GNU ELPA, so the barrier > to it becoming integrated into emacs (in whatever way) is low (or at > least, not dominated by questions of copyright assignment). I think the barrier is pretty high,

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Nicolas, Nicolas Goaziou writes: > The first important thing to understand is that, even if we enable > `org-tempo' by default, next Org release /will break/ for some of us. > > - It will break because `org-tempo' is only 99% backward-compatible. So > anyone having

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Aaron, Aaron Ecay writes: > Interesting. I didnʼt know about that function. I just tried M-x > customize-changed RET Org 9.0 RET. That gives an error; it seems to > only work based on emacs versions and not package versions. Thatʼs > unfortunate, it would have been

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Rasmus, Rasmus writes: > There’s tools to mark thinks as obsolete in Emacs should we need to. One problem is that those tools (I'm thinking of define-obsolote-*) are more developer-oriented than user-oriented. E.g. AFAIK there is no "tool" to tell a user that a command

[O] Smooth transition for modules (was: [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]"))

Hi Aaron, Aaron Ecay writes: > OK, thatʼs good to know. Iʼve held off on any pushing of the patch to > master until everything is worked out. In the meantime, Iʼve put it in > a branch “org-tempo”. thanks for this. > I also added a second commit to that branch which

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Aaron, Aaron Ecay writes: > As a general (idealized) principle, I think user-visible changes should > be phased in over at least one org major version. I have no problem > with “intrusive” deprecation warnings, but abrupt changes in behavior > should be avoided. I

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Rasmus, Rasmus writes: >> For org-tempo, Rasmus wrote it so I'm inclined to listen quite >> carefully at his opinion. > > Please don’t. Done :) > I have not really made any policy decisions of sort. I only missed > "

Re: [O] [POLL] Should Org tempo be enabled by default? (expand templates thru e.g. "<s[TAB]")

Hi Bernt, Bernt Hansen writes: > > *** Change in the structure template expansion > > Org 9.2 comes with a new template expansion mechanism, combining > ~org-insert-structure-template~ bound to