Re: [O] Proposal: references from code to text.

I believe you can do that with the Library of Babel ( https://orgmode.org/worg/org-contrib/babel/library-of-babel.html) John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213

Re: [O] Proposal: references from code to text.

interesting package! but i'm not sure it would work with org as well as org-link-minor-mode does. On 5/16/18, John Kitchin wrote: > You might want to check out linkd: https://www.emacswiki.org/emacs/linkd.el > > It does a lot of what you describe independently of

Re: [O] Proposal: references from code to text.

You might want to check out linkd: https://www.emacswiki.org/emacs/linkd.el It does a lot of what you describe independently of org-mode. John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh,

Re: [O] Manual: "ellipsis, special symbol", but no "ellipsis"

Nicolas Goaziou writes on Wed 16 May 2018 21:04: > "and =...= becomes a compact set of dots" refers to ellipsis. Ah... Sorry, I was not aware of the typographical meaning of the word. Thanks for the clarification. -- EOST (École et Observatoire des Sciences de la Terre) IPG (Institut de

[O] Bug: Spell checking language not set correctly when exporting to ODT [9.1.13 (9.1.13-elpa @ /home/christoph/.emacs.d/elpa/org-20180514/)]

When exporting an org document to ODT, the language used for spell checking is always set to British English. The TOC's name is actually translated to the language specified in the org document but the spell checking language is not set correctly. It is particularly weird that it is set to British

Re: [O] Parsing of todo state log lines

Hi Nicolas On Wed, May 16, 2018 at 10:42 PM, Nicolas Goaziou wrote: > I didn't test logging, but `org-skip-over-state-notes' definitely goes > past the three items, so I guess `org-log-beginning' should put point at > the end of the three items, too. Indeed, it works

Re: [O] Parsing of todo state log lines

Michael Brand writes: > I still get the new log in the middle line with > release_9.1.13-757-g463664b after restarting Emacs. Did you get the > new log after the last line? I didn't test logging, but `org-skip-over-state-notes' definitely goes past the three items,

Re: [O] Parsing of todo state log lines

Hi On Wed, May 16, 2018 at 10:08 PM, Nicolas Goaziou wrote: > You are right. It should be empty, not "". I think I fixed it in maint. I still get the new log in the middle line with release_9.1.13-757-g463664b after restarting Emacs. Did you get the new log after the

Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...]

Hello, alain.coch...@unistra.fr writes: > In general, though, I still feel it would make sense to document it, > especially considering that other ways than the default are already > documented. Consider this excerpt from section "6.2 Setting tags": > > Org supports tag insertion based on

Re: [O] Parsing of todo state log lines

Hello, Michael Brand writes: > I don't see this happen: When starting with this (the % and the > ordering of the lines have been edited manually) > > - State "DONE" from "TODO" [2018-05-15 Tue 10:00] > - State "DONE" from "%" [2018-05-15

Re: [O] [bug] in capture

Hello, Thomas Holst writes: > I have among other the following template: > > #+begin_src emacs-lisp > ("hr" "Rechnung erfassen" table-line >   (file+function "~/git/org-priv/Univ_Beih.org" > th:capure-find-open-vers-regn) >   "| # | %^u | %^{Arzt/Apotheke} | %^{fr

Re: [O] Parsing of todo state log lines

Hi Nicolas On Wed, May 16, 2018 at 9:07 PM, Nicolas Goaziou wrote: > Hello, > > Michael Brand writes: > >> There seems to be an inconsistency in parsing. When >> org-log-states-order-reversed is nil (which I am new to) and a TODO >> with the

Re: [O] Parsing of todo state log lines

Hello, Michael Brand writes: > There seems to be an inconsistency in parsing. When > org-log-states-order-reversed is nil (which I am new to) and a TODO > with the manually written state log lines > > - State "DONE" from "TODO" [2018-05-12 Sat] > - State

Re: [O] Proposal: references from code to text.

i'm not sure if i understand the goal. is it babel-only? this email might be off-topic. what i want is links, using something like org-id, - from non-org [for example, a link in file.el in a comment] - to non-org [for example, a named or id'ed location in the same file] - or to org [e.g.

Re: [O] Manual: "ellipsis, special symbol", but no "ellipsis"

Hello, alain.coch...@unistra.fr writes: > Hello. In the "Concept index", I see item "ellipsis, special > symbol:", but, going there, I see no mention of "ellipsis", which I > find strange. #+cindex: shy hyphen, special symbol #+cindex: dash, special symbol #+cindex: ellipsis,

Re: [O] Footnotes in the manual (hidden option?)

Hello, Kaushal Modi writes: > I would think that's so because canonically Org mode using [fn:1] style. It > looks like you are manually typing the footnote refs and definitions. > > Try using C-c C-x f binding.. you will see that Org inserts the footnotes > in the

Re: [O] Footnotes in the manual (hidden option?)

Hello, On Wed, May 16, 2018 at 2:27 PM ST wrote: > Hello, > > in the manual > > https://orgmode.org/manual/Footnotes.html#Footnotes > > it says that footnotes[fn:1] > > [fn:1] look like this > > > but actually[1] > > [1] works as well and looks even better. > > So why this

[O] Footnotes in the manual (hidden option?)

Hello, in the manual https://orgmode.org/manual/Footnotes.html#Footnotes it says that footnotes[fn:1] [fn:1] look like this but actually[1] [1] works as well and looks even better. So why this option is not documented? Thank you!

[O] Manual: "ellipsis, special symbol", but no "ellipsis"

Hello. In the "Concept index", I see item "ellipsis, special symbol:", but, going there, I see no mention of "ellipsis", which I find strange. Regards -- EOST (École et Observatoire des Sciences de la Terre) IPG (Institut de Physique du Globe) | alain.coch...@unistra.fr 5 rue René Descartes

Re: [O] Proposal: references from code to text.

* Main document See [[id:BAD97113-3561-4A4A-BA07-0CD5BF6BA35F][There is a reason we only support two args]] (text to text) for notes about this function. The addition is done in line [[(add)]] (text to code). Here we put names on different kinds of elements so we can put them into a tangled file

[O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...]

Nicolas Goaziou writes on Fri 4 May 2018 23:44: > > Incidentally, shouldn't this variable be documented in the > > manual? (Section "6.2 Setting tags" would seem a natural place > > for that.) I had to resort to internet search... > I don't know specifically about this one, but not all

[O] bug#31468: 24.5; org mode do not export current heading

Michel Damiens writes: [please keep the bug address in CC ] > Hello > my og-mode version is 9.1.13 > I'm not able to upgrade to emacs-26 for the moment : I'm not working on my > own system. > How do you think that sort of problem would depend on emacs version ?

Re: [O] Proposal: references from code to text.

Oh, that makes sense. So in this way, we must put the text into quotes, and then into a txt code block. And also we don't have a chance to do any transformation of the text(e.g. org-mode list to javadoc format).   I think the direct reference from code to text is better. I will try to implement