Re: Thoughts on the standardization of Org

Maxim Nikulin writes: > 2020-11-08 Jean Louis wrote: >> That is right, I am using it since years in ~/.mailcap that works well >> for mutt email client. >> >> text/org;emacsclient %s; nametemplate=%s.org; >> text/x-org; emacsclient %s; nametemplate=%s.org; > > Just for curiosity, couldn't

Re: Viewing link information

Hi Russell, I am using Doom Emacs, and in its default Org configuration it does exactly that: the link target is shown in the minibuffer after a brief delay, when the cursor is on the link. A bit of investigation reveals that it's using org-eldoc. This seems to be the code responsible for it:

Emails are not safe - Re: Thoughts on the standardization of Org

* Tim Cross [2020-11-10 00:50]: > > Maxim Nikulin writes: > > > 2020-11-08 Jean Louis wrote: > >> That is right, I am using it since years in ~/.mailcap that works well > >> for mutt email client. > >> > >> text/org; emacsclient %s; nametemplate=%s.org; > >> text/x-org;emacsclient %s;

Re: [PATCH] org-refile.el: Add org-refile-reverse which toggles org-reverse-note-order

On Sun, Sep 06, 2020 at 02:10:09AM -0400, Amin Bandali wrote: Bastien writes: Hi Adam, Adam Spiers writes: This is useful for prepending to the start of the target headline instead of appending to the end, or vice-versa depending on org-reverse-note-order. I think this would be useful.

Re: [PATCH] repeat cookies should be in the same order as the repeats

Thanks for the patch. > [PATCH] repeat cookies should be in the same order as the repeats Convention nit: Ideally this subject would start with a "scope/file:", e.g. "manual:" or "org-manual.org:". Also, could you please add a changelog entry and TINYCHANGE cookie, as described at

Re: Thoughts on the standardization of Org

Greg Minshall writes: > Tim, > >> No email can be considered 100% safe. > > "e-mail doesn't kill people; e-mail readers kill people". i would guess > using 'cat -v' to read e-mail is 100% safe. even throwing in > uudecode(1), or whatever is needed to decode base64, (and then piping > through

Re: [PATCH] ob-java

ian martins writes: > Let me know how it goes. Hello again. It seems that you have changed some classloader settings in the new code. I have examples which used to work perfectly; now they still compile, but fail to run, throwing exception java.lang.NoClassDefFoundError explained here:

Re: Thoughts on the standardization of Org

:)

Re: Thoughts on the standardization of Org

Tim, > No email can be considered 100% safe. "e-mail doesn't kill people; e-mail readers kill people". i would guess using 'cat -v' to read e-mail is 100% safe. even throwing in uudecode(1), or whatever is needed to decode base64, (and then piping through 'cat -v', of course ), it's probably

[UPDATED PATCH] Re: add new link type "contact:" for org-contacts.el

You're right. Thanks for suggestion. I attached new patch now. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Mon,

How to set options for verbatim environments produced by org babel

I’m using the ~Verbatim~ environment from the fancyvrb package to display Org Babel results in my Beamer slides. The ~Verbatim~ environment accepts options for setting the font size among other things. This is useful when the output of a code block has longer lines that do not fit on a

Re: Is there possibility to provide back links to each finely grained part of Org file?

On Sunday, 8 Nov 2020 at 23:40, Jean Louis wrote: > I know that #names exist in HTML export for *** headings. Do they or > can they exist for every paragraph or item listed? Maybe not quite what you want but you can place anchors (aka targets) anywhere you want in your document using <>. I use

Re: How to set options for verbatim environments produced by org babel

On Monday, 9 Nov 2020 at 12:28, Titus von der Malsburg wrote: > Is there a way to set options for the verbatim environment in Org mode? I cannot answer your actual question but I achieve the same outcome in a different manner. I name my src blocks and then add LaTeX directives to the output as

Re: Is there possibility to provide back links to each finely grained part of Org file?

On 2020-11-09 at 03:38 -08, Eric S Fraga wrote... > On Sunday, 8 Nov 2020 at 23:40, Jean Louis wrote: >> I know that #names exist in HTML export for *** headings. Do they or >> can they exist for every paragraph or item listed? > > Maybe not quite what you want but you can place anchors (aka

Re: Is there possibility to provide back links to each finely grained part of Org file?

On Monday, 9 Nov 2020 at 15:04, Jean Louis wrote: > If you have any pointer where I could insert a filter before > exporting, let me know. You could use the org-export-before-processing-hook to process the document. It works on a copy of the buffer. I've used this in the past. There are other

Re: [PATCH] add new link type "contact:" for org-contacts.el

* stardiviner [2020-11-09 03:25]: > After waited some days, still no reponse, so I popup this email. > Can some Org maintainer review my patch? Thanks. > It does not changed org-contacts.el core logic. Just added a new link type. > Should be easy to review. If I may say, many people manage their

Re: Is there possibility to provide back links to each finely grained part of Org file?

* Eric S Fraga [2020-11-09 14:39]: > On Sunday, 8 Nov 2020 at 23:40, Jean Louis wrote: > > I know that #names exist in HTML export for *** headings. Do they or > > can they exist for every paragraph or item listed? > > Maybe not quite what you want but you can place anchors (aka targets) >

Re: [PATCH] ob-java

Hello Ian! ian martins writes: > Let me know how it goes. The new version seems to be sensitive to whitespace: # - * this one works #+begin_src java :classname Foo :results output public class Foo { public static void

Re: Thoughts on the standardization of Org

2020-11-08 Jean Louis wrote: That is right, I am using it since years in ~/.mailcap that works well for mutt email client. text/org; emacsclient %s; nametemplate=%s.org; text/x-org; emacsclient %s; nametemplate=%s.org; Just for curiosity, couldn't it lead to execution of arbitrary

Re: Thoughts on the standardization of Org

On 09/11/2020 15:04, Maxim Nikulin wrote: > 2020-11-08 Jean Louis wrote: >> That is right, I am using it since years in ~/.mailcap that works well >> for mutt email client. >> >> text/org;emacsclient %s; nametemplate=%s.org; >> text/x-org; emacsclient %s; nametemplate=%s.org; > > Just for

Re: Is there possibility to provide back links to each finely grained part of Org file?

* Eric S Fraga [2020-11-09 15:45]: > On Monday, 9 Nov 2020 at 15:04, Jean Louis wrote: > > If you have any pointer where I could insert a filter before > > exporting, let me know. > > You could use the org-export-before-processing-hook to process the > document. It works on a copy of the

Re: Thoughts on the standardization of Org

* Maxim Nikulin [2020-11-09 17:06]: > 2020-11-08 Jean Louis wrote: > > That is right, I am using it since years in ~/.mailcap that works well > > for mutt email client. > > > > text/org; emacsclient %s; nametemplate=%s.org; > > text/x-org; emacsclient %s; nametemplate=%s.org; > > Just for

org-sbe results in two prompts for each evaluated cell

Hello, using the org-sbe macro to evaluate a code block with table cells as input results in two prompts for each cell evaluated: one to confirm the evaluation of the code block passed as an argument to org-sbe and one to confirm evaluation of the code block dynamically generated by org-sbe. Is

Caching answer to prompt for code block execution

Hello, I am trying to use the org-sbe macro to compute values in an org table. This results in a (well, actually two, see my other recent email to the mailing list) prompt for execution of the relevant code block. This is unpractical when there are more than an handful of cells to be evaluated.

Re: Viewing link information

There is a shortcut to copy the link here . You could display it in the same way. On Fri, Oct 30, 2020 at 12:15 PM Russell Adams wrote: > Are there other ways to view information about an org link that I > don't list below? > > - M-x