"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
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 I found it's slow one some big Org file and
writes:
>> "Processing is done through the command specified in
>> `org-texinfo-info-process',
>> which see."
>>
>> I think it is sufficient to remove the "which see" at the end.
>
> I think this is just the English incarnation of the customary Latin
> "q.v." [1], which in printed text used to
On Wed, May 24, 2023 at 08:24:21PM +0200, Niall Dooley wrote:
> The `org-texinfo-compile' docstring contains the following sentence which ends
> abruptly.
>
> "Processing is done through the command specified in
> `org-texinfo-info-process',
> which see."
>
> I think it is sufficient to remove t
The `org-texinfo-compile' docstring contains the following sentence which ends
abruptly.
"Processing is done through the command specified in `org-texinfo-info-process',
which see."
I think it is sufficient to remove the "which see" at the end.
Thanks for Org and your time.
On Wed, 24 May 2023 at 16:55, Ihor Radchenko wrote:
> > Aside, when invoking this command on an org file I get the following error
> > which may or not be a bug also:
> >
> > org-compile-file: File "/org-gtd.el/doc/org-gtd.info"
> > wasn’t producedSee "Org INFO Texinfo Output" for details
>
> It w
Niall Dooley writes:
> The `org-texinfo-export-to-info' docstring describes a non-existing optional
> argument PUB-DIR but no such argument is given in the definition. Perhaps
> it
> did in the past?
Yup.
Fixed, on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix&id
The `org-texinfo-export-to-info' docstring describes a non-existing optional
argument PUB-DIR but no such argument is given in the definition. Perhaps
it
did in the past?
Aside, when invoking this command on an org file I get the following error
which may or not be a bug also:
org-compile-file:
Emmanuel Charpentier writes:
> #+begin_src jupyter-apl :exports both :results raw :post
> html2text(data=*this*)
> ⍳7
> #+end_src
>
> #+RESULTS:
> #+begin_export html
>
> 1 2 3 4 5 6 7
> #+end_export
>
> but what /enrages/ me is that the (correct) result is still wrapped in an
> HTML block
Dear list,
I stumbled on the conversion of an HTML Babel export block to a "normal" Babel
output. What follows is the *verbatim* transcript of an org file explaining and
demonstrating the problem :
```
# Attempt to use emacs-jupyter to insert Dyalog APL org-src blocks.
#+options: author:nil to
"Tory S. Anderson" writes:
> ... But untouched was the type of key-menu I really want to hide when,
> for example, I hit =C-c a= =org-agenda= and get a menu of agenda
> options to choose from, or =(org-clock-goto '(4))= and I get a big
> indexed list of clock items. I don't mind keeping the fast
Andrea Lazzarini writes:
> I now wonder if there is a way to prevent changing
> eldoc-echo-area-use-multiline-p
> to nil globally to prevent footnotes from appearing there and not only in the
> eldoc-doc-buffer.
See the docstring for `eldoc-documentation-functions' - you can call the
CALLBACK d
Hi Andrea,
Andrea writes:
> I believe you could do something like that (borrowed from the LaTeX Wikibook):
> #+LATEX_HEADER: \hypersetup{
> #+LATEX_HEADER: colorlinks=true,% false: boxed links; true:
> colored links
> #+LATEX_HEADER: linkcolor=red, % color of internal l
Payas Relekar writes:
> I've been playing with org-footnote-assistance, and this is again just
> another opinion, but I'm also preferring the indirect buffer. It just
> puts things in better perspective.
I'd prefer to integrate things with `org-edit-special', if possible.
Possibly extending `org
Patrick Useldinger writes:
> On 20/05/2023 22:01, Ihor Radchenko wrote:
>> You can try to bisect your config to identify which part is triggering
>> the problem. See
>> https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
>> https://github.com/Malabarba/elisp-bug-hunter
>
> I have been
15 matches
Mail list logo
