I often create tables programatically from within an org code block. To make
sure I don’t produce multiple copies of the output, I like to enclose the
results in a drawer. However, the exporter seems to ignore any caption I might
assign if the table itself is inside a drawer. For example, if
Eldoc functionality only works after a restricted set of commands (see
the variable 'eldoc-message-commands'). Because `org-self-insert-
command', by default, is not in that list, eldoc functionality works
poorly in org-mode (it does not work when typing, only when navigating).
This patch fixes it
From: Daniel Nicolai
---
lisp/org-eldoc.el | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lisp/org-eldoc.el b/lisp/org-eldoc.el
index 5b4f66d..7137c46 100644
--- a/lisp/org-eldoc.el
+++ b/lisp/org-eldoc.el
@@ -54,6 +54,8 @@
:group 'org-eldoc
:type 'string)
+(eldoc-add-command
"Christopher M. Miles" writes:
> I'm the developer of Org mode package "org-link-beautify"
> https://repo.or.cz/org-link-beautify.git . The package main theory
> is to use org-link-parameters `:activate-func` to do link file preview
> with generating thumbnail images or file content etc.
>
> But
[ For some reason, an answer posted yesterday seems to have been lost.
Rewriting/reposting... ]
Nice answer ! I suppose that this is more a misdesign than a bug (limited goals
of Dyalog,that emacs-jupyter cannot alleviate).
Your suggestion worked. But now, I have to pass to my `:post` function
Hello,
I have just created a patch for org-eldoc.el in org-contrib.
I tried to send it using the 'Prepare a patchset' functionality on
sourcehut which
requires me to enter some email-address for where to send it to.
As I have no idea where to send it, I simply filled in the address of this
dalanicolai writes:
> I have just created a patch for org-eldoc.el in org-contrib.
> I tried to send it using the 'Prepare a patchset' functionality on
> sourcehut which
> requires me to enter some email-address for where to send it to.
> As I have no idea where to send it, I simply filled in
~dalanicolai writes:
> Eldoc functionality only works after a restricted set of commands (see
> the variable 'eldoc-message-commands'). Because `org-self-insert-
> command', by default, is not in that list, eldoc functionality works
> poorly in org-mode (it does not work when typing, only when
"Ihor Radchenko" wrote:
> bvchg...@mail.com writes:
> Parse tree is not kept in sync with the original buffer when you
> retrieve it by `org-element-parse-buffer'.
Okay, thanks. I thought that might be the case, but couldn't be sure.
> We generally do not currently
> have a way to modify Org
After calling, say, org-element-adopt-elements, do I (or rather my code)
have to do anything to make the modified tree apply to the Org document/
buffer that the tree came from?
I can see that the tree is modified but it isn't reflected in the buffer
it came from, and furthermore calling
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I'm the developer of Org mode package "org-link-beautify"
>> https://repo.or.cz/org-link-beautify.git . The package main theory
>> is to use org-link-parameters `:activate-func` to do link file preview
>> with generating thumbnail
copropriete27ruemo...@gmail.com writes:
> [ For some reason, an answer posted yesterday seems to have been lost.
> Rewriting/reposting... ]
You did not CC Org mailing list.
> Nice answer ! I suppose that this is more a misdesign than a bug (limited
> goals of Dyalog,that emacs-jupyter cannot
bvchg...@mail.com writes:
> After calling, say, org-element-adopt-elements, do I (or rather my code)
> have to do anything to make the modified tree apply to the Org document/
> buffer that the tree came from?
Yes. Parse tree is not kept in sync with the original buffer when you
retrieve it by
bvchg...@mail.com writes:
>> But be aware
>> that interpreted tree and the original text do not have exact 1-to-1
>> equivalence. Some whitespace might be lost.
>
> Only whitespace? I can live with that.
I know for sure about whitespace. We have some tests for interpreter,
but this has never
Bruno Cardoso writes:
> On 2023-05-22, 10:49 +, Ihor Radchenko wrote:
>
>> Thanks!
>> May you also update the docstring of `org-return-follows-link' and add
>> etc/ORG-NEWS entry?
>
> Hi Ihor, here's the updated patch as suggested.
Thanks!
I modified the patch, adding the necessary non-nil
Thanks, for the quick merge. And noted... :)
On Thu, 25 May 2023 at 13:03, Ihor Radchenko wrote:
> ~dalanicolai writes:
>
> > Eldoc functionality only works after a restricted set of commands (see
> > the variable 'eldoc-message-commands'). Because `org-self-insert-
> > command', by default,
Niall Dooley writes:
>> It would help if you provided more details. Ideally, steps to reproduce
>> the problem. See https://orgmode.org/manual/Feedback.html#Feedback
>
> I dug a little deeper. `org-tex-info-export-to-info' calls
> `org-texinfo-compile' which in turn calls `org-compile-file'. In
On 13/11/2021 12:39, Carlos Pita wrote:
in a clean emacs-28 install I do:
M-x package-install org
I get:
Possible completions are:
org-contrib org-edna org-real org-translate orgalist
I have realized that the command is specified in the README.org file, so
it is
Ah great, good to know... thanks again!
On Thu, 25 May 2023 at 12:57, Ihor Radchenko wrote:
> dalanicolai writes:
>
> > I have just created a patch for org-eldoc.el in org-contrib.
> > I tried to send it using the 'Prepare a patchset' functionality on
> > sourcehut which
> > requires me to
19 matches
Mail list logo
