[O] [patch] Check org-structure-template-alist

2018-05-27 Thread Rasmus
Hi, Here’s a patch that would check org-structure-template-alist for the "old" format. It just pops a user-error if the old format is detected (it checks if the cdr of org-structure-template-alist entries is a list). On my system, binding max-mini-window-height seems to have no effect. My test

Re: [O] extract a column from a table but but an name on the new table

2018-05-27 Thread Uwe Brauer
> On 26/05/2018 10:32, Uwe Brauer wrote: > You may like the out-of-the-boxtable remote references: > | 3 | > | 4 | > | 6 | > | 7 | > | | > | | > #+TBLFM: $1=remote(raw-data,@@#$3) > The downside is that you need to create an empty table with the right >

Re: [O] RFC: Proposal for an Org Special Block for ox-html

2018-05-27 Thread Aaron Ecay
Hi Kaushal, [...] > But then I also wanted to mask all the shortcoming of Markdown. So ox-hugo > helps bridge that gap by filling in HTML snippets only where needed. I hope > that makes sense. It does indeed make sense, thanks for the explanation. Now I understand the context a bit better. I

Re: [O] unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode

2018-05-27 Thread Aaron Ecay
Hi Nicolas, 2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen: [...] > > Also, we are in feature freeze for Org 9.2, so this would need, in any > case, to wait for the release. > > As a consequence, would you mind reverting the patches related to this > feature? Of course, done in

Re: [O] Babel - :export-dir and :file-ext arguments cause all blocks to emit files

2018-05-27 Thread Aaron Ecay
Hi Nicolas, 2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen: > > Hello, > > Aaron Ecay writes: > >> Iʼve pushed commit 1643f70d3 to master which documents this behavior. > > Thank you. Please have a look at the consistency edits I made to it. Thanks very much. (As

Re: [O] C++ is not accepted for SRC block evaluation

2018-05-27 Thread Aaron Ecay
Hi Nicolas, 2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen: [...] > No, that's not correct. It should be (C++ . t), but "ob-C.el" should > provide "ob-C++" feature, too. Is this right? Even if the feature is provide-d by the file, the require in org-babel-do-load-languages will not find

Re: [O] Babel - :export-dir and :file-ext arguments cause all blocks to emit files

2018-05-27 Thread Nicolas Goaziou
Aaron Ecay writes: > (As an aside: is org-footnote-auto-adjust TRT for the manual? It seems > like it will lead to lots of churn every time a footnote is added or > removed...) This is a trade-off, indeed. It adds churn in diffs, but it's more natural to follow when

Re: [O] unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode

2018-05-27 Thread Nicolas Goaziou
Aaron Ecay writes: > Of course, done in c32938b7f. I did not realize how the freeze for 9.2 > was working. Thank you. BTW, I'm considering creating a "next" branch for pending patches that I'm refraining to push to master. It could help moving forward. >> However, your

Re: [O] C++ is not accepted for SRC block evaluation

2018-05-27 Thread Nicolas Goaziou
Aaron Ecay writes: > Is this right? Even if the feature is provide-d by the file, the require > in org-babel-do-load-languages will not find it (because the file name > does not match). C++ is not a valid choice for the variable AFAICT. The > customize interface makes

[O] point moves and zoom level reverts when refreshing agenda

2018-05-27 Thread Samuel Wales
recent maint, have not tried in -Q. summary: point moves and zoom level reverts when refreshing agenda 1] i find that, when i do an agenda agenda [daily/weekly] and i have point on a task, and i go do something in the task and nearby nodes, and a bunch of other things, and return to the

Re: [O] point moves and zoom level reverts when refreshing agenda

2018-05-27 Thread Samuel Wales
On 5/27/18, Samuel Wales wrote: > 2] i also find that refreshing resets the zoom level created using > text-scale-increase. i wonder if this can also be preserved. to me, > refreshing refers to updating the contents of the agenda view, not > things like text scale.

[O] unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode

2018-05-27 Thread Van L
Hello. Is it possible to edit a buffer in org mode and its indirect-buffer in fundamental mode without losing pretty printing in the org mode base buffer? At the indirect-buffer, I switch to fundamental mode and that causes the base buffer in org mode to lose the pretty printing for

Re: [O] Problem with completion and case in tag search

2018-05-27 Thread Alain . Cochard
Nicolas Goaziou writes on Sun 27 May 2018 22:14: > > The file ~/tmp/bug-agenda.org contains > > > >* foo :bar:baR:Bar:BAR: > > > > When in the empty document ~/tmp/bug-agenda2.org, > > > > if I type > > > >C-a m > > > > it gives "BAR" in the minibuffer. > > > > If I type > >

[O] [fr] separate agenda buffers for different types of agenda

2018-05-27 Thread Samuel Wales
this is a separate report from my previous report about keeping point when refreshing. i think it is unrelated. i find myself doing a daily/weekly agenda, and often running an agenda text search, and thus losing my place in the daily/weekly. i am aware of c-c a *, but that also has the feature

Re: [O] extract a column from a table but but an name on the new table

2018-05-27 Thread Thierry Banel
On 26/05/2018 10:32, Uwe Brauer wrote: > You may name the Lisp block like that: > -- > #+TBLNAME: raw-data > | 1 | a | 3 | > | 2 | b | 4 | > | 3 | c | 6 | > | 4 | d | 7 | Thank you! BTW I found it strange that the extracting

Re: [O] unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode

2018-05-27 Thread Aaron Ecay
Hi Van, What you describe is fragile and should not work. OTOH, we need to provide a way to edit those curly braces. I have just pushed commit 102832e66 to the master branch. That will cause any sub/superscript under the point to have its font lock properties removed, so that the braces will

Re: [O] unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode

2018-05-27 Thread Nicolas Goaziou
Hello, Aaron Ecay writes: > OTOH, we need to provide a way to edit those curly braces. I have just > pushed commit 102832e66 to the master branch. That will cause any > sub/superscript under the point to have its font lock properties > removed, so that the braces will

Re: [O] Babel - :export-dir and :file-ext arguments cause all blocks to emit files

2018-05-27 Thread Nicolas Goaziou
Hello, Aaron Ecay writes: > Iʼve pushed commit 1643f70d3 to master which documents this behavior. Thank you. Please have a look at the consistency edits I made to it. > Iʼm inclined not to make the change now, but (hopefully remember to) > revisit it when Org 10 is

Re: [O] Problem with completion and case in tag search

2018-05-27 Thread Nicolas Goaziou
Hello, alain.coch...@unistra.fr writes: > I run > >emacs -Q -l ~/tmp/scr.emacs > > The file ~/tmp/scr.emacs contains > >(add-to-list 'load-path "~/.emacs.d/elpa/org-20180521/") >(setq org-agenda-files '("~/tmp/bug-agenda.org")) >(global-set-key "\C-ca" 'org-agenda) >

Re: [O] C++ is not accepted for SRC block evaluation

2018-05-27 Thread Nicolas Goaziou
Hello, Van L writes: >> John Kitchin writes: >> >> It should be (C . t) >> >> it looks like ob-C also handles C++. > > How about the following to update the documentation: > > #+BEGIN_EXAMPLE > diff --git a/doc/misc/org.texi b/doc/misc/org.texi > index cf1c037..7b00f0a

Re: [O] [patch] Check org-structure-template-alist

2018-05-27 Thread Aaron Ecay
Hi Rasmus, 2018ko maiatzak 27an, Rasmus-ek idatzi zuen: [...] > If there’s any better way to display the error org-display-warning? [...] > + (mapconcat 'identity > + '("Please update the entries of `%s'." > + "" > + "In Org 9.2 the format

Re: [O] Babel - :export-dir and :file-ext arguments cause all blocks to emit files

2018-05-27 Thread Aaron Ecay
Hi Alex, 2018ko maiatzak 25an, Alex Fenton-ek idatzi zuen: [...] > Now I understand how it was intended (a shortcut for people who are > scrupulous about using #+NAME) it makes sense. Iʼve pushed commit 1643f70d3 to master which documents this behavior. > I was thinking it was meant as an