Re: idea for capture anywhere in x

2020-09-08 Thread Maxim Nikulin
08.09.2020 12:21, Tim Cross wrote: How you add this to a window manager menu or key binding will depend on your window manager, but essentially, you just calling emacscleint with the argument -e (org-capture). You may need to quote the command to prevent shell interpolation of the command and

Re: [FEATURE REQUEST] No tangle of code blocks within archived subtrees

2020-09-08 Thread Tom Gillespie
Great, thank you. Also handy to see the "right" way to traverse up the tree. Best! Tom On Sun, Sep 6, 2020 at 9:52 PM Bastien wrote: > > Thanks Tom for the feedback. > > >> - org-babel-exp-process-buffer > > Yes > >> - org-babel-ref-resolve > > Probably not? > >> -

Re: Bug: Exporting internal link to special latex block [9.3.7 (9.3.7-14-gb2b587-elpa @ /home/lobo/.emacs.d/elpa/org-20200720/)]

2020-09-08 Thread Nicolas Goaziou
Hello, Bastien writes: > Marco Falconi writes: > >> Also, my preference would be for the exported id to be the one given >> in the NAME attribute (as it is now), because I use it in the html >> file to name the theorem environment. Of course this is just my >> preference, and I would

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread Bastien
Hi No Wayman, I pushed 4f49ebb6d, a small variant of your initial patch, which pass the test fine by checking whether the variables are bound outside or not, ignoring them if not. Thanks again for the fix! -- Bastien

Re: idea for capture anywhere in x

2020-09-08 Thread Diego Zamboni
Doom Emacs has an 'org-capture' script that uses emacsclient to externally invoke a new frame with 'org-capture' in it. Maybe this could be a good starting point? https://github.com/hlissner/doom-emacs/blob/develop/bin/org-capture --Diego On Tue, Sep 8, 2020 at 9:19 AM Maxim Nikulin wrote: >

Re: [PATCH] Re: Re: Re: org-forward-heading-same-level and the invisible-ok argument

2020-09-08 Thread Bastien
Hi D, D writes: >> Then, can as well use `mapcar', or even simply manual loop over line >> positions. > > How about this? I applied a small variant of it as a700fadd7, thanks. (See also the comment I added with f17d301e1, which basically means that such changes are made as exceptions.) --

eldoc recursion error

2020-09-08 Thread Matt Price
I know there have been a couple of updates to org-eldoc lately. After updating to current master, I get this error in source blocks if eldoc mode is turned on: eldoc error: (error Lisp nesting exceeds ‘max-lisp-eval-depth’) Is there an easy fix for this? is it a generic eldoc problem or

Re: [feature request] org-at-timestamp-p should accept multiple parameters

2020-09-08 Thread Bastien
Hi Adam, thanks, but I still need to understand the exact change you suggest and what general fix/improvement it will provide. Probably a patch will be easier to understand for this. Thanks, -- Bastien

Re: eldoc recursion error

2020-09-08 Thread Matt Price
On Tue, Sep 8, 2020 at 10:25 AM Bastien wrote: > Hi Matt, > > can you provide a recipe to reproduce the problem? > > oops, sorry, that was stupid. In a new org file, add these lines: #+begin_src python print #+end_src position cursor inside block and the error message occurs.

Re: eldoc recursion error

2020-09-08 Thread Bastien
Hi Matt, Matt Price writes: > In a new org file, add these lines: > > #+begin_src python > print > #+end_src > > position cursor inside block and the error message occurs. I can't reproduce the bug. What version of Emacs are you using? Can you give a recipe starting with emacs -q? Thanks!

Re: eldoc recursion error

2020-09-08 Thread Bastien
Hi Matt, can you provide a recipe to reproduce the problem? Thanks, -- Bastien

Re: eldoc recursion error

2020-09-08 Thread Matt Price
On Tue, Sep 8, 2020 at 10:53 AM Bastien wrote: > Hi Matt, > > Matt Price writes: > > > In a new org file, add these lines: > > > > #+begin_src python > > print > > #+end_src > > > > position cursor inside block and the error message occurs. > > I can't reproduce the bug. What version of Emacs

Re: [feature request] org-at-timestamp-p should accept multiple parameters

2020-09-08 Thread Adam Faryna
Ok, maybe I misunderstood the purpose of this function. I wanted to use it to check if the timestamp is active or inactive and I tried to get it by using (org-at-timestamp-p 'inactive) while pointing at the timestamp. But actually when I call it on any timestamp like [2020-09-04 Fri], <2020-09-04

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread Jack Kamm
Kyle Meyer writes: > That's on a Debian system with the python executable pointing to Python > 2.7.16. If I set org-babel-python-command to python3 (3.7.3) at the top > of test-ob-python.el, I see the same thing. I haven't dug any farther > yet. Jack, presumably you don't see the stall on

Re: Help debugging R source code block output problem with :session

2020-09-08 Thread Jack Kamm
"Berry, Charles" writes: > Also, I wonder if the `:results value' case can be handled in a similar > manner, viz. > > - (let ((tmp-file (org-babel-temp-file "R-"))) > + (let ((tmp-file (with-current-buffer session (org-babel-temp-file "R-" Yes, if we did that then tmp-file would have a

Re: idea for capture anywhere in x

2020-09-08 Thread Maxim Nikulin
08.09.2020 15:03, Diego Zamboni wrote: Doom Emacs has an 'org-capture' script that uses emacsclient to externally invoke a new frame with 'org-capture' in it. Maybe this could be a good starting point? https://github.com/hlissner/doom-emacs/blob/develop/bin/org-capture Thank you for the

Re: [feature request] org-at-timestamp-p should accept multiple parameters

2020-09-08 Thread Adam Faryna
I think the problem is general. If you work with any timestamp that is agenda like, you can't check using this function if it's active or inactive. The one solution would be to remove parameter "agenda" and consider every timestamp as a agenda like (the "timestamp" in " org-at-timestamp-p" suggest

Re: Help debugging R source code block output problem with :session

2020-09-08 Thread Jack Kamm
Hi Chuck, > this is already present in `org-babel-R-evaluate-session' in the call to > `org-babel-comint-eval-invisibly-and-wait-for-file'' just a couple of lines > further down in the `(cl-case result-type (value ...))' branch. > > The other use of `tmp-file' in that block is the one that

Re: Help debugging R source code block output problem with :session

2020-09-08 Thread Berry, Charles
Jack, Maybe I am confused here: > On Sep 8, 2020, at 7:51 AM, Jack Kamm wrote: > > Yes, if we did that then tmp-file would have a prefix like > "/scp:user@hostname:", and elisp would then know to read the result file > from the remote host. > > Before pasting tmp-file into R code, we should

[PATCH] org-element: Hide parsers boilerplate into plist-creating macros

2020-09-08 Thread akater
We replace some repetetive code with macro calls org-prog-plist and org-let*-prog-plist. The macros are not very conventional but hopefully their docstrings are illustrative enough. In effect, all subexpressions of the form :begin begin :end end :contents-begin contents-begin :contents-end

Re: eldoc recursion error

2020-09-08 Thread Matt Price
On Tue, Sep 8, 2020 at 11:27 AM Matt Price wrote: > > > On Tue, Sep 8, 2020 at 10:53 AM Bastien wrote: > >> Hi Matt, >> >> Matt Price writes: >> >> > In a new org file, add these lines: >> > >> > #+begin_src python >> > print >> > #+end_src >> > >> > position cursor inside block and the error

Re: idea for capture anywhere in x

2020-09-08 Thread Ihor Radchenko
> is something like this possible? It's very easy. Below is a part of my capture (bash) script for qutebrowser: emacsclient "org-protocol://capture?template=$TEMPLATE=$URL=$TITLE=$SELECTED_TEXT=$QUTE_HTML=$QUTE_FIFO" Best, Ihor Samuel Wales writes: > dunno if this is sensible, but istr you

Re: idea for capture anywhere in x

2020-09-08 Thread No Wayman
I use a deamon specifically for this. Here's a gist with my setup (thought slightly out of date, this will work as a base): https://gist.github.com/progfolio/af627354f87542879de3ddc30a31adc1

Re: Babel: parse error when output contains opening bracket

2020-09-08 Thread ian martins
Of course there's never a problem in fixing things. I'm curious how you did it. Will look when I have a chance. On Sun, Sep 6, 2020, 5:57 AM Bastien wrote: > Hi Ian, > > ian martins writes: > > > I've written an alternative org-java.el that doesn't have that > > problem. > > I hope you don't

Re: idea for capture anywhere in x

2020-09-08 Thread Samuel Wales
On 9/7/20, Maxim Nikulin wrote: > 08.09.2020 12:05, Samuel Wales wrote: >> well for a non-emacs application, i want to select text and capture >> using wm menu. > > Do you mean a tiny tool that takes content of X primary selection or > clipboard and passes it to emacs-client org-protocol

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread No Wayman
Jack Kamm writes: Also, could you try executing some simple ob-python session blocks and see if they hang? e.g., #+begin_src python :session :results output print(1+1) #+end_src #+begin_src python :session :results value 1+1 #+end_src These both work for me now on master as of

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread No Wayman
Bastien writes: Hi No Wayman, I pushed 4f49ebb6d, a small variant of your initial patch, which pass the test fine by checking whether the variables are bound outside or not, ignoring them if not. Thanks again for the fix! Sounds good to me! Thanks, Bastien.

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread No Wayman
Kyle Meyer writes: As I mentioned in the message linked upstream, it doesn't happen when running just test-org/org-read-date (BTEST_RE='test-org/org-read-date'), so there's some sort of interaction between tests. Sorry, I was a little late getting to this, and it seems to be resolved-

Re: [PATCH] org-add-planning-info: respect caller's given time [9.3.7 (release_9.3.7-716-g3d4876 @ /home/n/.emacs.d/straight/build/org/)]

2020-09-08 Thread Kyle Meyer
Jack Kamm writes: > No, the tests don't stall on my end (Archlinux with manually compiled > emacs 28). I also tested on a debian10vm and the tests passed there too. > > But since we know it's related to 4df12ea39 that gives some > clues...could you try the attached patch to see if it fixes

Re: idea for capture anywhere in x

2020-09-08 Thread Maxim Nikulin
09.09.2020 05:40, Samuel Wales wrote: On 9/7/20, Maxim Nikulin wrote: Do you mean a tiny tool that takes content of X primary selection or clipboard and passes it to emacs-client org-protocol argument? maybe. guessing probably. i want it to take contents of x primary selection or clipboard

Re: [PATCH] Re: Re: Re: org-forward-heading-same-level and the invisible-ok argument

2020-09-08 Thread Ihor Radchenko
> I applied a small variant of it as a700fadd7, thanks. > > (See also the comment I added with f17d301e1, which basically means > that such changes are made as exceptions.) For record, the old behaviour did not only affect a single external package. For example,

Re: Bug: [PATCH] org-datetree-insert-line doesn't honor headline spacing customization [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

2020-09-08 Thread Vasilij Schneidermann
Hello Bastien, > Thanks for the patch. I tried it and these two tests fail: > >FAILED test-org-datetree/find-date-create >FAILED test-org-datetree/find-iso-week-create > > Perhaps you can check the value of `org-blank-before-new-entry' and > insert a blank line only if needed? I've

variable-pitch-mode misaligns org-mode heading tags

2020-09-08 Thread Protesilaos Stavrou
1. Run 'emacs -Q' 2. Open a new Org file 'C-x C-f /tmp/test.org' 3. Insert the following contents: * TODO this is a test :tag: * TODO here is another test :tag: The tags should align to the right with

Re: [PATCH] Re: Re: Re: org-forward-heading-same-level and the invisible-ok argument

2020-09-08 Thread D
Hi Bastien, > I applied a small variant of it as a700fadd7, thanks. thank you! > (See also the comment I added with f17d301e1, which basically means > that such changes are made as exceptions.) I fully understand, though I do believe that this change is beneficial to the way