Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> May I know if you are still interested to work on the patch?
>
> I was hoping someone else (TM) would implement it once we figure out
> what we want. :) That said, I can put it on my to-do list, but it will
> be a while, as I am currently *s
Hi Org,
I realized the function `org-babel-tangle-comment-links' won't return the
relative file path regardless of the value of
`org-babel-tangle-use-relative-file-links', is this the intended behaviour
or a bug? Here's the source code for `org-babel-tangle-comment-links' for
reference:
(defun or
Ihor Radchenko writes:
> Thanks, but I have some concerns.
Of course you do. :)
> This won't work. js-comint.el hard-coded buffer name to be
> "*Javascript REPL*". We cannot change that.
Fixed. I replaced the change with a comment to inform the reader that
JS is miscapitalized on purpose, so
>From "emacs -Q":
Save the attached file, make it ready-only, visit the file, move point
to the start of the line with the first checkbox, type C-C C-c. I get a
message "Cannot update this checkbox". That's fine, the file and buffer
are read-only.
-*-org-*-
- [ ] box1
- [ ] box2
- [ ] box3
-
Hello,
I want to print a bibliography in my Org document and I use
`#+print_bibliography:`.
But when I do, it automatically create a section with a title. And
I want it to not create a section. Only insert in the section where I
call the print.
How can I do ?
signature.asc
Description: PGP si
Elle Najt writes:
> Hi -- I've been running into a bug when running async + session bash
> org babel cells.
>
> * Summary
> In short, the issue is that when running two async session bash
> blocks, the code for the second block ends up captured in the output
> of the first one, and then finally
Richard Sent writes:
> * lisp/ox-texinfo.el (org-texinfo-src-block): Preserve the language
> field during export.
> * etc/ORG-NEWS (Version 9.8): Add news entry.
> ---
> Hello all,
>
> When exporting source blocks to Texinfo, the language is removed
> (unless it is lisp). This hurts the ability t
Daan Ro writes:
>> `string-match-p' matching the strings directly.
> A candidate may have multiple appearances, like
> "Author A ;; Author B ;;; ..."
> `string-match-p' would only find the first ";;" and miss
> ";;;". I thought s.el's `s-match-strings-all' should be more robust but
> we can't use
l...@phdk.org writes:
> When adding a newline to an org-src block with
> `org-src-tab-acts-natively' set to t, if there's a non-whitespace
> character following the pointer at insertion, all other lines are
> indented by an additional `org-edit-src-content-indentation'
> regardless of their origin
Billy Lei writes:
> Subject: [PATCH] org-preview-latex-process-alist: Add xdv support for latex
> preview
>
> * lisp/org.el (org-preview-latex-process-alist): Add new process "xelatex" to
> allow using xelatex to generate latex preview.
Thanks for the patch!
> :image-size-adjust (1.7 .
Rob Ward writes:
> I am getting this and other errors, including but not limited to
> "org-back-to-heading: Before first headline at position 7503 in buffer
> 01032025 [3 times]", "Added org-data parent to non-headline element" and
> others which appear to relate to parsing failures, when I edit
Rudolf Adamkovič writes:
> Okay, it was not me, and I have reproduction steps to prove it:
>
> 1. Create ~/test.org with the following content:
> ...
> 2. Execute emacs -Q
> 3. Type C-x C-f ~/test.org RET
> 4. Type M-x flyspell-mode RET
> 5. Place the cursor on the first heading star
> 6. Record
Rudolf Adamkovič writes:
> There is a typo in the docstring, BTW.
>
> See the attached patch.
Applied, onto bugfix, after amending the commit message.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?h=bugfix&id=5df37854739baa67006dc1cda70fab6a42977880
--
Ihor Radchenko // yantar92
Ihor Radchenko writes:
> Also M-y would be counter-intuitive because it usually means very
> different thing (M-y is `yank-pop' by default).
Agreed.
There is a typo in the docstring, BTW.
See the attached patch.
>From c4451d2f946d8699a131b0c8473eac51b636d0c3 Mon Sep 17 00:00:00 2001
From: =?U
Ihor Radchenko writes:
> May I know if you are still interested to work on the patch?
I was hoping someone else (TM) would implement it once we figure out
what we want. :) That said, I can put it on my to-do list, but it will
be a while, as I am currently *swamped* with "life". If all goes well
Ihor Radchenko writes:
> This will be a breaking change that will surprise users familiar with
> current behavior of image previews and latex previews.
But will it be a pleasant surprise? :)
Is there any other part of Org where action like this is not recursive?
For example, when running source
Rudolf Adamkovič writes:
>> This won't work. js-comint.el hard-coded buffer name to be
>> "*Javascript REPL*". We cannot change that.
>
> Fixed. I replaced the change with a comment to inform the reader that
> JS is miscapitalized on purpose, so that this will not happen again.
Almost :)
> ---
"Michael P. Soulier" writes:
> Got this while entering a journal note. It happened when I hit C-c C-c
> to save it.
>
> ⛔ Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org
> buffer # (org-agenda-mode)
> ⛔ Warning (org-element): org-element--cache: Org parser error in
> jo
Rudolf Adamkovič writes:
> BTW, Flyspell also makes Org with large files *terribly* slow.
>
> To reproduce:
>
> (add-hook 'text-mode-hook #'flyspell-mode)
> (add-hook 'prog-mode-hook #'flyspell-prog-mode)
>
> [This is the recommended way of enabling Flyspell.]
>
> Then open a very large and compl
Richard Sent writes:
> * lisp/ox-texinfo.el (org-texinfo-src-block): Preserve the language
> field during export.
Ha! I have the exact same patch in works. I also asked on the Texinfo
Help mailing list [1] whether this will break compatibility with older
Texinfo versions (like @math did, where
> >> > + ;; Handle regexp separator?
> >>
> >> Is it a TODO?
>
> You missed this question.
Previously I didn't think of handling regexp-based separator argument,
but then since you said
> regexp-opt will be safer if separator happens to be something like
> ".".
so I opted to always assume litera
l...@phdk.org writes:
> [1] I think this is what this thread was about:
> https://list.orgmode.org/CALp=Ckko1Ck7-3K+bfKXLVSqDJvmHWYEZutkj5J2v3t=quv...@mail.gmail.com/T/#tO
>
> Which was closed as not a bug, but since I feel I'm misunderstanding
> either the original report or Ihor's answer I tho
When adding a newline to an org-src block with
`org-src-tab-acts-natively' set to t, if there's a non-whitespace
character following the pointer at insertion, all other lines are
indented by an additional `org-edit-src-content-indentation'
regardless of their original indentation.
MRE with -Q on t
* lisp/ox-texinfo.el (org-texinfo-src-block): Preserve the language
field during export.
* etc/ORG-NEWS (Version 9.8): Add news entry.
---
Hello all,
When exporting source blocks to Texinfo, the language is removed
(unless it is lisp). This hurts the ability to use the Texinfo files
to generate ad
On 21/03/2025 20:54, Rudolf Adamkovič wrote:
Re-capitalize "Javascript" to JavaScript.
Are there potential legal issues with the registered trademark owned by
Oracle? E.g. organizers of JSConf avoid "JavaScript" in the conference title
https://www.trevorlasn.com/blog/oracle-javascript-tradema
25 matches
Mail list logo
