Re: [O] [PATCH] org-agenda: Store stuck project redo command

maybe i got that backward. my note is: "fixme bug in org: either if you do g, it will ignore restriction lock or you have to manually remove restriction lock. the best would be for g to preserve the restriction lock even though it has been removed." On 4/20/17, Samuel Wales wrote: > in case it

Re: [O] [PATCH] org-agenda: Store stuck project redo command

in case it isn't already considered, i think storing the conditions of the original call applies to many agenda calls. i run into this issue with the following old code. i set a restriction lock, and run agenda, but g runs agenda without the restriction lock. (defun alpha-org-agenda-subtree (&op

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

The (xxx) form for a link target, especially one outside of a block, doesn't seem to have meaning within the document model that Org understands. So, yes, this explains *why* I am seeing the error described above. But I still think there is a legitimate bug report here, since the behaviour is not

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Joe Corneli writes: > In my opinion, capture and/or search should do something different for > text beginning "(" and ending with ")", when this text is a link > target that is not within a code block. See below. > The docs say: > > "In literal examples, Org will interpret strings like ‘(ref:n

Re: [O] Bug: entering range of times [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Yeah the problem has been resolved after restarting Emacs. I think the old version had new files but not everything had been loaded, so it was indeed mixed.

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

On Thu, Apr 20, 2017 at 8:35 PM, Nicolas Goaziou > Joe Corneli writes: >> Debugger entered--Lisp error: (error "No match for coderef: like this") > > The error message should give you the answer. Links within parenthesis > denote "coderefs". See (info "(org) Literal examples"). > > [[file:~/test.t

Re: [O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Hello, Joe Corneli writes: > I've noticed a problem with the link system. > > Reproduction steps. > > 1. Find any text in a file, surrounded by parentheses (like this). > > 2. org-capture the region in parentheses to come up with, e.g., > > ** TODO This is a problem >(like this) >[[file:

Re: [O] Bug: Canceling a TODO state change does not revert the heading [9.0.5 (9.0.5-elpa @ /home/laurence/.emacs.d/elpa/org-20170210/)]

Hello, Laurence Rochfort writes: > If you change the TODO state with org-todo and it accepts a message, but > you then cancel the message with C-c C-k, org does not revert the TODO > heading to its previous state. > > For instance: > > Heading is TODO > C-c C-t -> Set to WORKING > Prompted for m

[O] elisp call dot babel doesn't work on Org mode 9

Hi, I like generating simple process diagrams using dot and tables tutorial! It works fine on Org mode 8 but doesn't work on Org mode 9.0.5. The reason is the params variable not accessible! below error message displayed: let: Symbol’

[O] org-src--contents-for-write-back : preserve original major-mode, and avoid mixing tabs and spaces in org-mode buffers

Hi, I found a bug in org-mode where emacs-lisp code that is in a already-indented source block in an org-mode buffer is improperly indented when editing it via C-c '. Take the following contrived example emacs-lisp source code: 1. Here is a list item with a emacs-lisp source block: #+BEGIN_S

[O] Bug: Incomplete header-args parsing [9.0.5 (9.0.5-elpa @ ~/.emacs.d/elpa/org-20170210/)]

org-babel-parse-header-arguments stops parsing arguments after an argument with a string value containing unbalanced parentheses. For example: ELISP> (org-babel-parse-header-arguments ":foo \"(foo\" :bar 123") ((:foo . "(foo")) Whereas with balanced parentheses: ELISP> (org-babel-parse-hea

[O] Bug: Canceling a TODO state change does not revert the heading [9.0.5 (9.0.5-elpa @ /home/laurence/.emacs.d/elpa/org-20170210/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. --

Re: [O] How to obtain the headline level from org-element-at-point

Hello, Thanks for the reply. > what do you mean it only considers level 1 headlines? It seems to work on all > headlines for me. I mean that interleave-mode doesn't find the pdf path if I use the following configuration. That is property at level 2 headline. * Literature ** Notes for

[O] No explicit way to add blank lines to the beginning or end of example or source blocks

No explicit way to add blank lines to the beginning or end of example or source blocks. For example: describing HTTP header: --- HTTP header consists of colon-separated name-value pairs, and terminated by a CRLF character sequence, e.g

Re: [O] Bug: entering range of times [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Joe Corneli writes: > As I understand it I should be able to enter a range of times using > either of the following formats: > > ** TODO time range <2017-04-21 Fri 15:45-16:45> > ** TODO time+date range <2017-04-21 Fri 15:45>--<2017-04-22 Sat 15:45> > > Docs: http://orgmode.org/manual/Timestamps.

[O] Bug: entering range of times [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

As I understand it I should be able to enter a range of times using either of the following formats: ** TODO time range <2017-04-21 Fri 15:45-16:45> ** TODO time+date range <2017-04-21 Fri 15:45>--<2017-04-22 Sat 15:45> Docs: http://orgmode.org/manual/Timestamps.html However, using the formats a

[O] Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]

Hello, I've noticed a problem with the link system. Reproduction steps. 1. Find any text in a file, surrounded by parentheses (like this). 2. org-capture the region in parentheses to come up with, e.g., ** TODO This is a problem (like this) [[file:~/test.tex::(like%20this)]] 3. Now try

Re: [O] Export in Foswiki format?

"Loris Bennett" writes: > Hi, > > I'm interested in exporting from Org to Foswiki format. Is > org-export-generic.el still the way to go or has this been superseded by > something else? Nevermind, I found this: https://github.com/dfeich/org8-wikiexporters also available via MELPA. Cheers,

[O] Export in Foswiki format?

Hi, I'm interested in exporting from Org to Foswiki format. Is org-export-generic.el still the way to go or has this been superseded by something else? Cheers, Loris -- This signature is currently under construction.

Re: [O] [babel] Working dir incorrect

Hi, "Loris Bennett" writes: > Hi John, > > John Hendy writes: > >> On Mon, Mar 13, 2017 at 9:32 AM, Loris Bennett >> wrote: >>> Hi, >>> >>> In a file that used to work, when I now try to run some R code which >>> generates an image, I get the error: >>> >>> cannot open file './usage_users_hi

Re: [O] inline markup within quote

Rasmus writes: > AFAIK the quote block is irrelevant here. Perhaps you could customize > org-emphasis-regexp-components (this will only work if Hugo uses Emacs to > generate html). IIRC, Hugo uses native parser for org-mode: https://github.com/chaseadamsio/goorgeous > There’s also a thorough