Re: Bug Report: Invalid Function Error after Natively Compiling =org-element=

Ihor Radchenko writes: > Vitus Schäfftlein writes: > >> After updating to emacs version 30.1 from version 29.4.4, I experience >> issues with =org-element-with-disabled-cache=. Specifically, creating an >> =org-roam= node with a template that sets a =#+category= yields the error >> =invalid-f

Re: Bug Report: Invalid Function Error after Natively Compiling =org-element=

Vitus Schäfftlein writes: > After updating to emacs version 30.1 from version 29.4.4, I experience issues > with =org-element-with-disabled-cache=. Specifically, creating an =org-roam= > node with a template that sets a =#+category= yields the error > =invalid-function org-element-with-disable

Re: Bug Report: Org Agenda 'custom-initialize-reset: Cache must be active'

Zan Owsley writes: > My apologies - I realised the mistake in how I changed how I was setting > 'org-agenda-files'. Continued head-banging was what I needed. No problem. Closing. Canceled. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at .

Re: Bug Report: Org Agenda 'custom-initialize-reset: Cache must be active'

My apologies - I realised the mistake in how I changed how I was setting 'org-agenda-files'. Continued head-banging was what I needed. Zan On 12/10/24 11:06 AM, Zan Owsley wrote: Hi, Emacs version: 30.0.92. I had been using org-agenda fine for a while with the new version, but this just st

Re: Bug report for ox-icalendar: newlines should be CRLF

Jack Kamm writes: > I've pushed this change now: > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4446ce795c924a1e115e360d3674f6ad89be845 Fixed. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development a

Re: Bug report for ox-icalendar: newlines should be CRLF

Jack Kamm writes: > writes: > >>> > There is a related issue about EOLs, not just \r\n -- each line should >>> > be a maximum of 75 characters; this is handled by >>> > org-icalendar-fold-string >>> >>> May you please provide a link to the iCalendar spec document section >>> describing this r

Re: Bug report for ox-icalendar: newlines should be CRLF

> It's in rfc5545 [1], referenced to from rfc7986 [2]. yes, that's it. There is also this validator that can check files against the spec: https://icalendar.org/validator.html Stpehen

Re: Bug report for ox-icalendar: newlines should be CRLF

writes: >> > There is a related issue about EOLs, not just \r\n -- each line should >> > be a maximum of 75 characters; this is handled by >> > org-icalendar-fold-string >> >> May you please provide a link to the iCalendar spec document section >> describing this requirement? > > It's in rfc55

Re: Bug report for ox-icalendar: newlines should be CRLF

On Fri, Apr 14, 2023 at 10:13:48AM +, Ihor Radchenko wrote: > "Stephen J. Eglen" writes: > > >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996 > > > > Thanks for copying me in on this. > > > > There is a related issue about EOLs, not just \r\n -

Re: Bug report for ox-icalendar: newlines should be CRLF

"Stephen J. Eglen" writes: >> https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b51891996 > > Thanks for copying me in on this. > > There is a related issue about EOLs, not just \r\n -- each line should > be a maximum of 75 characters; this is handled by > org-

Re: Bug report for ox-icalendar: newlines should be CRLF

> Ihor Radchenko writes: > >> Sorry for the late reply. >> >> Do I understand correctly that all the ical lines must use \r\n? [1] > > Following up here that I have pushed a fix for the EOL issue in > ox-icalendar: > > https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab57879

Re: Bug report for ox-icalendar: newlines should be CRLF

Ihor Radchenko writes: > Sorry for the late reply. > > Do I understand correctly that all the ical lines must use \r\n? [1] Following up here that I have pushed a fix for the EOL issue in ox-icalendar: https://list.orgmode.org/87355ikzwk.fsf@localhost/T/#m180c100587d3d88ab5787942271a546b5189199

Re: Bug report for ox-icalendar: newlines should be CRLF

"Stephen J. Eglen" writes: > The lines from BEGIN:VEVENT to CATEGORIES:test inclusive have CR (^M) as well > as LF (^J) as newline [in the text above, I've converted the ^M to *** > to see them eaer. Is that intended? Uploading the file to > https://icalendar.org/validator.html gives me the err

Re: Bug report for ox-icalendar: newlines should be CRLF

Hello, just to confirm. The exporter is inconsistent in adding which kind of EOL sequence. Detlef Am Fri, 06 Jan 2023 08:30:41 + schrieb "Stephen J. Eglen" : > Hello, > > If I have a test file > > -- > > * test 1 > > <2

Re: Bug report: org-preview-latex fails when using tramp

Timothy writes: > Confirmed. > > I just tried this by creating an Org file on a Debian server (I run OpenSUSE > with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, > it > appears that the temp file is created on my local machine, and then the > process > is called on th

Re: Bug report

Looks like I was trying to be too clever. :) I used org-mode to write the bug report. The problem isn't that the formatting fails in source code blocks. I put it in one so that it would appear verbatim. If you copy the contents of the block into a normal paragraph, you should be able to see the

Re: Bug report

On Wednesday, 1 Jun 2022 at 23:24, Max Nikulin wrote: > > I think, it is org and #+begin_src is used to demonstrate a snippet of > org markup, so to reproduce the problem try it in a regular paragraph. Ah, sorry, missed the point entirely! -- : Eric S Fraga, with org release_9.5.3-520-g4dda0d

Re: Bug report

On 01/06/2022 22:37, Eric S Fraga wrote: On Wednesday, 1 Jun 2022 at 07:53, Topi Mäenpää wrote: I have trouble escaping a dollar sign in org-mode documents. I tried to enter the following: #+begin_src A (14 G$) B (6 G$) #+end_src You may use entities: \dollar I have no problem with this.

Re: Bug report

On Wednesday, 1 Jun 2022 at 07:53, Topi Mäenpää wrote: > I have trouble escaping a dollar sign in org-mode documents. I > tried to enter the following: > > #+begin_src > A (14 G$) B (6 G$) > #+end_src I have no problem with this. What version of org are you using? Out of curiosity, what languag

Re: Bug report: org-preview-latex fails when using tramp

Confirmed. I just tried this by creating an Org file on a Debian server (I run OpenSUSE with TexLive 2021). From looking at the `*Org Preview LaTeX Output*' buffer, it appears that the temp file is created on my local machine, and then the process is called on the remote machine. ┌ │ This is

Re: Bug report: remote file python src output gives FileNotFound (+ suggested fix)

Hi Paul, I'm unable to reproduce the issue, and believe this issue has already been fixed in the latest version of org-mode. See this patch [1]. Could you please upgrade to Org 9.4 and test again? Thanks, Jack [1] https://orgmode.org/list/87h7t16red.fsf@pc.i-did-not-set--mail-host-address--so-t

Re: Bug Report: Broken Link in Worg

Hi Joshua, Joshua Meyers writes: > In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to > the "very instructive post by Pete Phillips" now directs to the > defunct gmane.org.  I think I tracked down the post it is supposed to > link to, so I don't want others to have to do this w

Re: org id update locations search sequence (was Re: bug report org mode)

Hi Samuel, I have difficulties understanding the proposal. Can you restate it as a MEC (Minimal Enhancing Change)? Thanks, -- Bastien

org id update locations search sequence (was Re: bug report org mode)

i have been wondering about the search sequence for this function. id updating is capable of being quite slow, which can be distracting when you follow a link and emacs hangs for a while, so i was thinking maybe this could be optimized. idk about data structures and searching, but i think the seq

Re: bug report org mode

Hi Siegmar, Siegmar Maier writes: > According to my examination the problem is with > org-id-update-id-locations. Removeing that column makes it work > again. > If I put that line behind it works also again Yes, `org-todo-keyword-faces' will be taken into account when set before any actual font

Re: [Orgmode] Re: Bug report: filing into a date tree in year 2011 when 2010 exists in file

On Jan 4, 2011, at 7:24 AM, Carsten Dominik wrote: What would be helpful is a minimal file that, as a date-tree target, reproduces the issue. I am sure the problem could then easily be found. If you want to follow the procedure yourself, do M-x debug-on-entry RET org-datetree-find-year-cr

Re: [Orgmode] Re: Bug report: filing into a date tree in year 2011 when 2010 exists in file

What would be helpful is a minimal file that, as a date-tree target, reproduces the issue. I am sure the problem could then easily be found. - Carsten On Jan 4, 2011, at 4:48 AM, Charles Cave wrote: Carsten Dominik gmail.com> writes: Strange, for me this worked without any problems this m

[Orgmode] Re: Bug report: filing into a date tree in year 2011 when 2010 exists in file

> Carsten Dominik gmail.com> writes: > Strange, for me this worked without any problems this morning. I have found that the new year was created in other files but it definitely misbehaves in my taskdiary.org file. I can only assume there is a pattern of characters that fools the algorithm fo

Re: [Orgmode] RE: Bug Report: refile and attachments

Colin Fraizer wrote: >I know it's not _exactly_ the same, but I re-filed it back to the original >file (C-c C-w) and then opened it successfully (C-c C-a o). It didn't >prompt me (because there was only one attachment). >I just tried it with a new entry and attachment file (of the same type) and

[Orgmode] RE: Bug Report: refile and attachments

Cc: 'emacs-orgmode Mailinglist' Subject: Re: Bug Report: refile and attachments "Colin Fraizer" writes: > 1. Exactly what I did > > I created an entry in an org file. > > I added an attachment to that entry. > > I used refile (C-c C-w) to move the entry

[Orgmode] Re: Bug Report: refile and attachments

"Colin Fraizer" writes: > 1. Exactly what I did > > I created an entry in an org file. > > I added an attachment to that entry. > > I used refile (C-c C-w) to move the entry to another org file. > Before doing this, can you try opening it from initial org file itself. using C-c C-a o Tha

Re: [Orgmode] Re: Bug Report for emacs 23 and follow-mode

No trouble. And welcome to the list. I'm not exactly sure what you meant by "mixed up with indirect buffers" and "technically valid, but unimportant". So do post back if you think there is still a significant bug. Scot On Tue, Jul 14, 2009 at 2:45 PM, Cian OConnor wrote: > How embarrassing. I

[Orgmode] Re: Bug Report for emacs 23 and follow-mode

How embarrassing. I was getting mixed up with indirect buffers. So while the bug report is technically valid, it seems fairly unimportant... Did I mention what a great product this is..? Cian OConnor wrote: Hi, I'm using a fairly recent build of Emacs 23 on windows (23.0.94.1), and while fol

[Orgmode] Re: bug report with org 5.11b and remember 1.19

On Wed, Oct 10 2007, Carsten Dominik wrote: > This happens because you are calling `remember-mode' interactively. > Org-mode assumes that the command you are using is either `remember' > or `org-remember'. What are you calling `remember-mode'? What are > you trying to achieve? Carsten-- So far

[Orgmode] Re: bug report with org 5.11b and remember 1.19

On Wed, Oct 10 2007, Carsten Dominik wrote: > This happens because you are calling `remember-mode' interactively. > Org-mode assumes that the command you are using is either `remember' > or `org-remember'. What are you calling `remember-mode'? What are > you trying to achieve? Carsten-- So far

[Orgmode] Re: [bug-report] inserting link to a target with non-ascii symbols

hmmm.. the bug is not always repeatable... sometimes link is inserted, sometimes not. now try to figure out exact conditions ___ Emacs-orgmode mailing list Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode