I tried the following but no stack-trace is produced:
rm -rf .emacs .emacs.d
cat > /tmp/agenda.org << orgfile
* Anniversaries
:PROPERTIES:
#+CATEGORY: Ann
:END:
%%(org-bbdb-anniversaries-future 3)
orgfile
emacs
package-install bbdb
bbdb-create
Just some name
(i)nsert a field "anniversary" for th
Ihor Radchenko writes:
> No extra information for over a month.
> I assume that the problem disappeared.
> Closing.
> Canceled.
Yes, Ihor. I was unable to reproduce the issue despite continued use of
the offending file.
Thanks,
Panos
Hello,
I'm trying to learn more about the publish export option or Org mode. Specifically I am using the
function `org-latex-publish-to-pdf` to export Orgmode files into PDF.
Since this export backend is transparently using Latex, there is stuff going on behind my back that
makes it a bit d
> See https://list.orgmode.org/87lek2up0w@tec.tecosaur.net/
> (https://link.getmailspring.com/link/37e53521-13cf-4156-93ed-196834780...@getmailspring.com/0?redirect=https%3A%2F%2Flist.orgmode.org%2F87lek2up0w.fsf%40tec.tecosaur.net%2F&recipient=ZW1hY3Mtb3JnbW9kZUBnbnUub3Jn)
Thank you, the said
Tommy Jollyboat writes:
> However, various functions within org-mode are still using
> ~string-to-char~ and giving inconsistent results, because numerical
> priorities are parsed wrongly, or sometimes return nil (or #10 to
> #64).
Confirmed.
> * SOLUTION
>
> If we agree that numeric priorities
(tested with Org 9.7.11, I've done my best to search archives and the
bug-tracker)
Back in 2020, commit #4f98694bf introduced numeric priorities,
allowing [#1] to [#64] as an alternative to [#A] to [#Z]. This is also
documented in the manual.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/c
Maxim Nikulin writes:
> It is rather annoying that C-c C-x p `org-set-property' may be quite
> slow if a file is large enough. (I do not consider it huge however.)
> There is noticeable delay before the prompt for property name appears in
> minibuffer. Accidentally I have noticed that sometime
"Dr. Arne Babenhauserheide" writes:
>> Today, I decided to start using Python in Org.
>>
>> (1) I read in "WORG":
>>
>> :results {output, value}: [...] Value results are the value of the
>> last expression evaluated in the code block. Value mode is the default
>> (as with other languages).
Daan Ro writes:
> Currently I have minor mode that automates `org-latex-preview` every some idle
> seconds so that newly typed fragments are automatically rendered. Having an
> option to disable messages would make Emacs's interface much cleaner.
You can suppress all the messages via `inhibit-me
a4ofu...@anonaddy.com writes:
> there is ambiguity right now if you want to org-store-link to heading 2
>> subheading 1. By default org stores
> [[file:::*subheading1]], which would incorrectly point to
> heading 1.
>
> Instead it could be [[file:::*heading 2**subheading1]]
>
> Please let me know
Akash Pal writes:
> Suppose we have the following document
>
> ```
> #+title: test-file
>
> * This is h1
>
> ** This is h1.2
>
> We introduce some text here
>
> Then we narrow to this heading and introduce a footnote
> ...
> When we narrow to h1.2 (subtree) so that * Footnotes is not visible - af
Suhail Singh writes:
> Additionally, and seemingly related, fontlocking for unindented
> anonymous and inlined footnotes is also broken. This can be observed
> via emacs -q and opening a file with the following contents:
>
> #+begin_example
> ** 9.7.11, 9.6.15
> [fn::This footnote has not fontlo
Suhail Singh writes:
> With Emacs -q, in a new org file, set ~org-footnote-define-inline~ to t.
> With point at the beginning of the line invoke =M-x org-footnote-new=.
>
> As implied in the syntax spec, inline and anonymous footnotes are
> permitted to occur on an unindented line (unlike a footn
Ihor Radchenko writes:
>> I had similar problems now and then, but this is the first time that
>> they don’t seem to stop again.
>
> Sorry, but I simply cannot use your recipe.
> See my previous attempt in
> https://list.orgmode.org/orgmode/878qz2tu2o.fsf@localhost/
>
> Nothing changed since that
Ihor Radchenko writes:
> If you can reproduce from emacs -Q, may your please share more detailed
> instructions on how to trigger the problem you are seeing?
No response for over a month.
Closing.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
Ihor Radchenko writes:
>> I am sending this report at the request of org's built in monitor. org mode
>> recovered gracefully and did not inconvenience me.
>>
>> I have attached my configuration state report.
>> ...
>
> Thanks for reporting!
> It looks like you encountered a bug in the parser.
>
Ihor Radchenko writes:
>> Expected behavior: File can be opened and worked on.
>
> It does not look like you are using the latest version of Org mode.
> Does the problem persist if you upgrade to the latest Org 9.7.11?
No response for over a month.
There is nothing I can do to help without the e
17 matches
Mail list logo