> What I am leaning towards now (although, I hope that more ideas can
> still surface in this thread), is simply re-using transient menu. Maybe
> with a couple of simple extensions (default action, menu UI, and the
> !arg macros we introduced).
>
> Then, we (or third-party packages) can implement c
> On Dec 22, 2024, at 21:22, Ihor Radchenko wrote:
>
> Applied, after adding TINYCHANGE cookie.
> https://git.sr.ht/~bzg/orgweb/commit/9cc4f344c89b20d002d8b65dd968b5fd8e45fbc9
Oops! Thank you!
-Aaron
Ihor Radchenko writes:
> I think that we should:
> 1. Remove this from Org 9.7 manual (bugfix)
> 2. Add a note that the one-liner requires Emacs 30 in the Org 9.8-re
>manual (main)
Fixed, on main, and on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=9f5fce73e9
https
"Fraga, Eric" writes:
> Response below/inline for email Ihor Radchenko wrote:
>> (original email sent 23 Dec 2024 at 15:10)
>>
>> Thanks for reporting!
>> I tried to add support for #+name'd elements in ox-texinfo.
>> See the attached patch.
>
> Seems to work fine, at least for both the minimal
Response below/inline for email Ihor Radchenko wrote:
> (original email sent 23 Dec 2024 at 15:10)
>
> Thanks for reporting!
> I tried to add support for #+name'd elements in ox-texinfo.
> See the attached patch.
Seems to work fine, at least for both the minimal test and my long
document. Thank
"Fraga, Eric" writes:
> but also happen to have a code block
>
> #+name: model
> #+begin_src ...
>
> exporting to texinfo, asking to refer to [[model]], creates a reference
> to an non-existing target ("model") because (a) org appears to assume
> that you wish to reference the src block, not the
Joseph Turner via "General discussions about Org-mode."
writes:
> I can export the following Org content to a .odt file, but the exported
> file cannot be opened ("Read Error. Format error discovered in the file
> in sub-document content.xml at 368,2(row,col).")
>
> --8<---cut here---
Rudolf Adamkovič writes:
> BTW, I am not sure if this is a known bug, but
>
> `org-babel-detangle' ignores the comment customizations,
>
> namely
>
> - org-babel-tangle-comment-format-beg and
> - org-babel-tangle-comment-format-end.
>
> As a result, the function, more likely than not,
>
>
"John Wiegley" writes:
> The following patch adds ‘org-archive-finalize-hook’, which runs earlier than
> ‘org-archive-hook’ and in the destination buffer, not the original file. This
> allows the context to be extended, the archived entry to be cleaned up after
> inseration, maybe even encrypted
Paul Stansell writes:
> In case it's relevant, I also frequently get warnings like the following:
>
> Warning (emacs): Emacs reader failed to read data in
> "~/.cache/org-persist//gc-lock.eld". The error was: "End of file during
> parsing"
May it be that you often have multiple Emacs processes r
* William Denton [2024-12-23 20:21]:
> On Monday, December 23rd, 2024 at 01:45, Jean Louis wrote:
>
> > Instead of following:
> >
> > | Column | | Column |
> > |---+---+---|
> > | The dog is happy | | The dog is happy |
> > | I am very happy | | I am
Paul Stansell writes:
> Occasionally, when I start emacs from the command line, I get this bug, but
> it's intermittent,
> so I have ignored it until now.
>
> All I can report is that I opened an org file named scratch.org and
> received the following error message:
>
> Warning (org-element): o
Hello Ihor,
May you add
> (setq org-element--cache-self-verify 'backtrace)
> to your config?
Sure, I'll do that.
In case it's relevant, I also frequently get warnings like the following:
Warning (emacs): Emacs reader failed to read data in
"~/.cache/org-persist//gc-lock.eld". The error was: "E
Ihor Radchenko writes:
> Karthik Chikmagalur writes:
>
...
Considering this, it might be better to just split
`org-link-preview-file' into two public functions, where the "inside"
function accepts an image instead of a file.
>>>
>>> Agree.
>>> Would you be interested to creat
On Monday, December 23rd, 2024 at 01:45, Jean Louis wrote:
> Instead of following:
>
> | Column | | Column |
> |---+---+---|
> | The dog is happy | | The dog is happy |
> | I am very happy | | I am very happy |
> | The dog is very happy | | The sun is
Okamsn via "General discussions about Org-mode."
writes:
> Markup structures like "#+begin_src" and "#+being_quote" can be
> inserted using the command `org-insert-structure-template'. In much
> of the documentation, these structures are called "blocks", including
> the existing documentation fo
Visuwesh writes:
> Sorry for the late reply. I was busy with uni.
No worries. My reply is no less late. For similar reasons.
> I have now done this in the attached patch. I use a temporary buffer to
> convert the table, and also decode it as per buffer-file-coding-system
> of the Org buffer a
Pedro Andres Aranda Gutierrez writes:
> yet another quirk to make org-beamer more comfortable to use:
>
> I was writing a presentation recently and needed a listing to appear as
> part of an animated slide. After some searching around, I found an elegant
> solution in [1]. I was wondering if this
Morten Kjeldgaard writes:
> The subject says it, it would be very nice if there was an export option
> to export to text mode without wrapping paragraphs,so the resulting text
> file can be read with visual-line-mode on.
See org-export-preserve-breaks. Does it do what you want?
--
Ihor Radch
[திங்கள் டிசம்பர் 23, 2024] Ihor Radchenko wrote:
>> I have now done this in the attached patch. I use a temporary buffer to
>> convert the table, and also decode it as per buffer-file-coding-system
>> of the Org buffer as I could not tell whether LibreOffice always uses
>> UTF-8 or not. I belie
>
> May it be that you often have multiple Emacs processes running
> simultaneously and killed by signal?
>
I do typically have multiple Emacs processes running simultaneously, but
I'm not aware that I kill Emacs processes, I either quit Emacs with C-x
C-c, or I click on the "X" in the top right o
On Thu, Dec 19, 2024 at 12:16 PM Ihor Radchenko wrote:
>
> Thanks in advance!
> Do note that we still cannot blindly replace every instance of
> buffer-file-name with the new function. At least a cursory case-by-case
> check is necessary to make sure that logic will not be broken.]
Understood,
With ~:results file~, the absence of ~:file~ will cause the filename to
be constructed from the block name and ~:file-ext~, if they are both
present. To achieve that with ~:results file link~, I could only come up
with
~:var outFile=(alist-get :file (nth 2 (org-babel-get-src-block-info
't)))~
Ha
23 matches
Mail list logo
