Paul Stansell writes:
> Please let us know if you keep seeing the error more than once.
>>
>> If you do, we will provide instructions how to get more debugging info,
>> so that we can figure out what exactly is going wrong.
>>
>
> Since I reported the first warning message in this thread, I've ha
> May you please add
>
> (setq org-element--cache-self-verify 'backtrace)
> (setq org-element--cache-self-verify-frequency 1.0)
>
> to your config?
>
Yes, I'll do that, thanks.
Tianshu Wang writes:
> I am seeking this support because when adding Attachments to Org File
> without Headlines, I get a user-error: Before first headline at position
> 1 in buffer filename.org, even if the attachment has been successfully
> added. I hope there are no errors, and the #+FILETAGS
"Tom Alexander" writes:
> I've written a patch (attached) with my proposed wording changes to
> the documentation, should I be starting another thread or does
> dropping it here work best?
You can just modify subject with [PATCH], as I did.
> ... I do not have commit access so I'd need
> someon
"Tom Alexander" writes:
> I've written a patch (attached) with my proposed wording changes to
> the documentation, should I be starting another thread or does
> dropping it here work best?
You can just modify subject with [PATCH], as I did.
> ... I do not have commit access so I'd need
> someon
Hello all,
I have a rather large & complex file which has many src blocks, all of
which tangle to a single file, defined by a header-args property.
When I try to tangle, I get the following (not very informative
unfortunately) backtrace:
Debugger entered--Lisp error: (wrong-type-argument stringp
"Fraga, Eric" writes:
> I have a rather large & complex file which has many src blocks, all of
> which tangle to a single file, defined by a header-args property.
>
> When I try to tangle, I get the following (not very informative
> unfortunately) backtrace:
>
> Debugger entered--Lisp error: (wro
Tommy Phillips writes:
> Here is a suggested small patch for how org hides emphasis markers.
> It's my first patch so hopefully I'm submitting it correctly.
The patch is ok. Thanks for submitting!
> Subject: [PATCH] lisp/org.el: Only hide-emphasis-markers that are in
> org-emphasis-alist
>
> *
Ihor,
On Thursday, 14 Sep 2023 at 12:40, Ihor Radchenko wrote:
> To debug, you can try to patch `org-babel-tangle-single-block', catching
> when `org-src-coderef-regexp' is called with nil argument (it must be a
> string). Then, examine which source block you are at when that happens.
Thank you.
Max Nikulin writes:
>> You can set `org-auto-align-tags' to nil.
>
> I saw it, but from its description I decided that its effect may be to
> broad. I have tried it and to my surprise it does not affect editing of
> heading, tags are kept aligned. M- and M- do not realign
> tags, so the value
"Fraga, Eric" writes:
> Ihor,
>
> On Thursday, 14 Sep 2023 at 12:40, Ihor Radchenko wrote:
>> To debug, you can try to patch `org-babel-tangle-single-block', catching
>> when `org-src-coderef-regexp' is called with nil argument (it must be a
>> string). Then, examine which source block you are at
Hi Ihor,
On Thursday, 14 Sep 2023 at 12:59, Ihor Radchenko wrote:
> For the patch, it will be something like adding (when ... (debug)) and
> evaluating the defun.
>
> The source block in question is at point, so, in the debugger, you can
> just do "e (point) " and then jump to that point manually.
Hi! I reply below:
Em [2023-09-10 dom 07:50:22+], Ihor Radchenko escreveu:
> One possible way to fix the confusion could be adding a new
> `org-export-async-preserve-global-state' variable. When non-nil, we
> will transfer global state in addition to the buffer-locals. But I
> would like t
Hi Ihor again,
> The source block in question is at point, so, in the debugger, you can
> just do "e (point) " and then jump to that point manually.
this did the trick. However, interestingly, the error was a src block
that ended with
+end_src
(somehow the "#" got deleted). What's interesting
Dear Vladimir,
while I do not have much experience with inline source blocks, at least
for regular source blocks, you can define a file-wide header argument by
adding a file property. This can be even language specific -- inside my
(literate) Emacs config, I have for example at the top of the fi
Emacs 29.1, org version 9.6.9
When encrypting an entry in org-mode using symmetric encryption
and gpg 2.2, emacs just hangs there on 'Saving file'.
Tried running a backtrace using emacs -Q, but no errors generated,
it just hangs there.
There is nothing wrong with gpg, I can encrypt/decrypt from t
16 matches
Mail list logo