Re: [O] Bug: Small error in [[info:org#The clock table]] [9.1.3 (9.1.3-10-gadfbfd-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20171127/)]

2017-11-29 Thread Nicolas Goaziou
Hello, Jorge Morais Neto writes: > The mentioned manual section says: > `C-c C-c or C-c C-x C-u (`org-dblock-update')' > Update dynamic block at point. The cursor needs to be in the > `#+BEGIN' line of the dynamic block. > > However, the docstring only says > Use

[O] Bug: Small error in [[info:org#The clock table]] [9.1.3 (9.1.3-10-gadfbfd-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20171127/)]

2017-11-29 Thread Jorge Morais Neto
The mentioned manual section says: `C-c C-c or C-c C-x C-u (`org-dblock-update')' Update dynamic block at point. The cursor needs to be in the `#+BEGIN' line of the dynamic block. However, the docstring only says User command for updating dynamic blocks. Update

Re: [O] [PATCH]: Fix ob-haskell.el to work with custom ghci prompts

2017-11-29 Thread Nicolas Goaziou
Hello, Doro Rose writes: > Nicolas Goaziou writes: > >> Hello, >> >> Doro Rose writes: >> >>> In summary, yes I'm accessing user settings but in a rather >>> noninvasive way. Unfortunately I can't think of a more elegant way to >>> do this. >> >> Let's put it differently then. Isn't it the job

Re: [O] [PATCH] make org-comment-dwim comment headings if on a heading

2017-11-29 Thread Nicolas Goaziou
Alex Branham writes: > Patch attached, thanks! Applied. Thank you. Regards,

Re: [O] [PATCH] Preserve point when calling org-capture in gnus virtual group

2017-11-29 Thread Nicolas Goaziou
Matt Lundin writes: > Thanks! And here is another patch to fix the same issue in temporary > nnir search groups in gnus. Applied. Thank you. Regards,

Re: [O] How to log changes to orgmode files?

2017-11-29 Thread Kyle Meyer
Mirko Vukovic writes: > When I invoke ChangeLog, it is pre-populated with the file name only. > There is no finer information about the location of the modification. For > instance, I would like to use the tree heading name or ID. > > Is there a standard way of logging changes? If I understand

Re: [O] How to log changes to orgmode files?

2017-11-29 Thread Colin Baxter
Hello Mirko, > Mirko Vukovic writes: > Hello, I am writing a report in org-mode (with pdf export). The > file is under git version control. I would like to log changes I > make to the document. > When I invoke ChangeLog, it is pre-populated with the file name > only. Ther

Re: [O] [PATCH] Preserve point when calling org-capture in gnus virtual group

2017-11-29 Thread Matt Lundin
Nicolas Goaziou writes: > Matt Lundin writes: > >> When calling org-capture in gnus virtual groups (for instance, groups >> created through searches), I found that the region captured was >> different than the region I had selected. This is because one of the >> functions called in org-gnus-stor

[O] What about a space when inserting a src-block?

2017-11-29 Thread Marco Wahl
Hi! My impression is that one always types a blank after calling `org-insert-structure-template' {C-c C-x w s} for creating a src block. Suggestion: Realize the insert of a space after "#+begin_src" in `org-insert-structure-template'. WDYT? Best regards, Marco

Re: [O] Results with #+begin_example/#+end_example don't get overwritten

2017-11-29 Thread Nicolas Goaziou
Hello, Kaushal Modi writes: > No, I wasn't suggesting a use case where someone writes the #+RESULTS: > contents manually. > > Here's what can happen though: > > A user could have this to begin with: [...] > Then for whatever reason, they choose to delete the RESULTS manually.. and > the blank

[O] How to log changes to orgmode files?

2017-11-29 Thread Mirko Vukovic
Hello, I am writing a report in org-mode (with pdf export). The file is under git version control. I would like to log changes I make to the document. When I invoke ChangeLog, it is pre-populated with the file name only. There is no finer information about the location of the modification. For

Re: [O] [PATCH] Preserve point when calling org-capture in gnus virtual group

2017-11-29 Thread Nicolas Goaziou
Hello, Matt Lundin writes: > When calling org-capture in gnus virtual groups (for instance, groups > created through searches), I found that the region captured was > different than the region I had selected. This is because one of the > functions called in org-gnus-store-link moves the point to

Re: [O] C++ code block not linked [SOLVED]

2017-11-29 Thread Roger Mason
Hello, Nick Dokos writes: > All very good info, but why did the OP not have a g++? Using a > non-linux operating system? Using a non-GNU tool chain? Inquiring > minds want to know... Running on FreeBSD 10.3, which uses clang/clang++ by default. That said, I _do_ have gcc 5.4.0 installed and a

Re: [O] [PATCH] make org-comment-dwim comment headings if on a heading

2017-11-29 Thread Alex Branham
On Wed 29 Nov 2017 at 13:46, Nicolas Goaziou wrote: > I also added TINYCHANGE at the end of the commit message. Please > consider signing FSF papers if you haven't done so. If you did, let me > know it so I can update our registry. I've signed the papers. > > Would you mind writing an entry in

[O] [PATCH] Preserve point when calling org-capture in gnus virtual group

2017-11-29 Thread Matt Lundin
When calling org-capture in gnus virtual groups (for instance, groups created through searches), I found that the region captured was different than the region I had selected. This is because one of the functions called in org-gnus-store-link moves the point to the end of the buffer. The attached p

Re: [O] Bug: Template Expansion with prompt-specific history [9.1.2 (9.1.2-37-g3f8d67-elpa @ /Users/ke/.emacs.d/elpa/org-20171113/)]

2017-11-29 Thread Nicolas Goaziou
Hello, Karl Eichwalder writes: > Template expansion no longer works as documented: > > %^{PROMPT} prompt the user for a string and replace this sequence with > it. > You may specify a default value and a completion table with > %^{prompt|default|completio

Re: [O] [PATCH] make org-comment-dwim comment headings if on a heading

2017-11-29 Thread Nicolas Goaziou
Hello, Alex Branham writes: > I've attached the updated patch (with a test), but the test fails > because calling M-x comment-dwim in an org buffer on a heading results > in the old behavior of comment-dwim rather than the new behavior. > Calling M-x org-comment-dwim directly works as I expect (