Re: [O] Bug: no more fontifying in org mode [9.1.14 (9.1.14-dist @ /home/abel/git-ext/org-9.1.14/lisp/)]
Hello, boris martin writes: > minimal-org.el --- > > ;;; Minimal setup to load latest 'org-mode' > > ;; activate debugging > (setq debug-on-error t > debug-on-signal nil > debug-on-quit nil) > (add-to-list 'load-path "~/git-ext/org-9.1.14/lisp") > (add-to-list 'load-path "~/git-ext/org-9.1.14/contrib/lisp" t) > > -- en minimal-org.el -- > > minimal file where the bug happens --- > > *sdfsd* > *aezraze* > /titi/ > > > - end minimal file where the bug happens - I cannot reproduce your issue. Could you try Org development version? Regards, -- Nicolas Goaziou
Re: [O] Footnotes in the manual (hidden option?)
Hello, ST writes: > I saw only "fn:" related variations in the docs... Indeed, but every variation needs to be handled specifically, so it ultimately counts as a different syntax. > Even if somebody else implements this and provides a patch?... Yes, please. This is a matter of design, not implementation. I'd like to stabilize Org syntax as much as possible. As a rule of thumb, I would only consider syntax changes only for: 1. broken syntax 2. missing feature 3. syntax hindering compatibility (e.g., conditional syntax) Regards, -- Nicolas Goaziou
Re: [O] Bug: BEGIN_SRC and BEGIN_EXAMPLE shortcuts? [9.1.14 (release_9.1.14-1035-gfeb442 @ /home/calvin/git/org-mode/lisp/)]
The new org-format manual in the git repo ( https://code.orgmode.org/bzg/org-mode/raw/master/doc/org-manual.org) already documents the new templates (search for "Structure Templates"), but I'm not sure if this is already available in rendered form somewhere. The manual at https://orgmode.org/manual/ still seems to be the old version. Best, --Diego On Wed, Nov 14, 2018 at 5:26 PM wrote: > > > The new shortcuts have the advantage of being able to wrap text - if you > have a region selected, it will be wrapped in the new block. > > Oh brilliant! I've always wanted to do that. Thanks! > > I think the manual might still have the old easy-templates thing > described? That or I somehow have the old version of the manual in emacs > still :). > > Diego Zamboni writes: > > > Hi Calvin, > > > > This changed in recent versions - the default keyboard shortcut now C-c > C-, followed by a letter to choose the type of block (s for src, e for > example, etc.). I think there's still a way > > to enable the old tab expansions, but I have gotten used to the new ones > by now. > > > > The new shortcuts have the advantage of being able to wrap text - if you > have a region selected, it will be wrapped in the new block. > > > > Best, > > --Diego > > > > On Wed, Nov 14, 2018 at 4:39 PM Calvin Beck > wrote: > > > > Remember to cover the basics, that is, what you expected to happen and > > what in fact did happen. You don't know how to make a good report? See > > > > https://orgmode.org/manual/Feedback.html#Feedback > > > > Your bug report will be posted to the Org mailing list. > > > > > > I recently upgraded org-mode to the most recent commit on the git > > development branch. Are > and example blocks no longer working? I type those, hit tab, and then > > nothing happens. The shortcuts do not get expanded to blocks. > > > > Thanks! I understand that this is the development version so it might > > not be stable, but the other issue I was having on the stable release > > (capture templates ruining headings) made it unusable for me. I > > apologize if this version is too new and spiffy to complain about :). > > > > Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu) > > of 2018-09-29 > > Package: Org mode version 9.1.14 (release_9.1.14-1035-gfeb442 @ > /home/calvin/git/org-mode/lisp/) > > > -- >
Re: [O] Bug: BEGIN_SRC and BEGIN_EXAMPLE shortcuts? [9.1.14 (release_9.1.14-1035-gfeb442 @ /home/calvin/git/org-mode/lisp/)]
> The new shortcuts have the advantage of being able to wrap text - if you have > a region selected, it will be wrapped in the new block. Oh brilliant! I've always wanted to do that. Thanks! I think the manual might still have the old easy-templates thing described? That or I somehow have the old version of the manual in emacs still :). Diego Zamboni writes: > Hi Calvin, > > This changed in recent versions - the default keyboard shortcut now C-c C-, > followed by a letter to choose the type of block (s for src, e for example, > etc.). I think there's still a way > to enable the old tab expansions, but I have gotten used to the new ones by > now. > > The new shortcuts have the advantage of being able to wrap text - if you have > a region selected, it will be wrapped in the new block. > > Best, > --Diego > > On Wed, Nov 14, 2018 at 4:39 PM Calvin Beck wrote: > > Remember to cover the basics, that is, what you expected to happen and > what in fact did happen. You don't know how to make a good report? See > > https://orgmode.org/manual/Feedback.html#Feedback > > Your bug report will be posted to the Org mailing list. > > > I recently upgraded org-mode to the most recent commit on the git > development branch. Are and example blocks no longer working? I type those, hit tab, and then > nothing happens. The shortcuts do not get expanded to blocks. > > Thanks! I understand that this is the development version so it might > not be stable, but the other issue I was having on the stable release > (capture templates ruining headings) made it unusable for me. I > apologize if this version is too new and spiffy to complain about :). > > Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu) > of 2018-09-29 > Package: Org mode version 9.1.14 (release_9.1.14-1035-gfeb442 @ > /home/calvin/git/org-mode/lisp/) --
Re: [O] Bug: BEGIN_SRC and BEGIN_EXAMPLE shortcuts? [9.1.14 (release_9.1.14-1035-gfeb442 @ /home/calvin/git/org-mode/lisp/)]
Hi Calvin, This changed in recent versions - the default keyboard shortcut now C-c C-, followed by a letter to choose the type of block (s for src, e for example, etc.). I think there's still a way to enable the old tab expansions, but I have gotten used to the new ones by now. The new shortcuts have the advantage of being able to wrap text - if you have a region selected, it will be wrapped in the new block. Best, --Diego On Wed, Nov 14, 2018 at 4:39 PM Calvin Beck wrote: > > Remember to cover the basics, that is, what you expected to happen and > what in fact did happen. You don't know how to make a good report? See > > https://orgmode.org/manual/Feedback.html#Feedback > > Your bug report will be posted to the Org mailing list. > > > I recently upgraded org-mode to the most recent commit on the git > development branch. Are and example blocks no longer working? I type those, hit tab, and then > nothing happens. The shortcuts do not get expanded to blocks. > > Thanks! I understand that this is the development version so it might > not be stable, but the other issue I was having on the stable release > (capture templates ruining headings) made it unusable for me. I > apologize if this version is too new and spiffy to complain about :). > > Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu) > of 2018-09-29 > Package: Org mode version 9.1.14 (release_9.1.14-1035-gfeb442 @ > /home/calvin/git/org-mode/lisp/) > >
[O] Bug: BEGIN_SRC and BEGIN_EXAMPLE shortcuts? [9.1.14 (release_9.1.14-1035-gfeb442 @ /home/calvin/git/org-mode/lisp/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. I recently upgraded org-mode to the most recent commit on the git development branch. Are
Re: [O] [feature] Handle recurrence in <> and [] dates
Hi! > Leo Gaspard writes: > >> Here is a translated example task from my .org file: >> >> *** TODO Check bank report >> SCHEDULED: <2000-02-10 Thu +1m> >> >> Dated [2000-01-01 Sat +1m] >> >> The point of this “Dated” field being to tell me to which report I >> should be looking, given I sometimes am a month late or so in checking >> my reports, and just put them in the (physical) drawer as I receive >> them. >> >> This “Dated” field is exactly what I would like to see updated when I >> mark the task as done (like the SCHEDULED date), but it looks like it >> doesn't move. > > Org didn't handle repeaters in inactive time stamps. This is now fixed > (in master). Thank you. AFAICT the performance of marking tasks done which contain *a lot* of inactive timestams has degraded considerably with this change. Example: #v+ * TODO task SCHEDULED: <2018-11-15 .+1d> :PROPERTIES: :STYLE:habit :LAST_REPEAT: [2018-11-14 16:26] :END: [2018-07-10 Tue 11:29]--[2018-07-10 Tue 12:10] [2018-07-09 Mon 15:20]--[2018-07-09 Mon 15:23] [2018-07-08 Sun 09:01]--[2018-07-08 Sun 09:20] ... ... [2013-07-08 Sun 09:01]--[2013-07-08 Sun 09:20] #v- Sorry for not having digged deeper into this issue yet. Ciao, Marco
Re: [O] Bug: Capture problems with newlines [9.1.14 (9.1.14-9-g131531-elpa @ /home/calvin/.emacs.d/elpa/org-20181105/)]
Aha! Finally figured out how to get this installed over the MELPA version.
Yes, this is fixed in the development branch. I am so happy about this. I hope
this is released in a stable version soon, because right now org-capture is
really destructive otherwise.
Thanks!
Nicolas Goaziou writes:
> Hello,
>
> Calvin Beck writes:
>
>> I have this problem where I have a capture template like this:
>>
>>> ("t" "Todo" entry (file+headline "~/org/todo.org" "Tasks")
>>>"* TODO %?\n SCHEDULED: %t\n %a\n")
>>
>> And then if I have another heading under Tasks...
>>
>>> * Tasks
>>> * HEADING2
>>
>> Then when capturing a todo entry, if I delete the last line I get something
>> like...
>>
>>> * Tasks
>>> ** TODO
>>>SCHEDULED: <2018-11-05 Mon>
>>>link* HEADING2
>>
>> And similarly, if I edit the last line in the capture template I get...
>>
>>> * Tasks
>>> ** TODO
>>>SCHEDULED: <2018-11-05 Mon>
>>>link
>>> the stuff that I added at the end of my capture template* HEADING2
>>
>> This is counter intuitive, as you expect the capture to be isolated from
>> the other headings. Additionally, it's not obvious that you are messing
>> up other headings when you are using org-capture, so you can end up
>> losing tasks and headings, which seems like a very bad behaviour!
>
> Could you test again with development version? I think it was fixed
> recently.
>
> Regards,
--
Re: [O] typo, sp at C++ Source Code Blocks in Org Mode
> my guess is that it would be a lot of work to mark up the Worg sources to get > well-formatted info output. The orgmode manual is going to be an org-file which I guess will output to info:org.
[O] Bug: no more fontifying in org mode [9.1.14 (9.1.14-dist @ /home/abel/git-ext/org-9.1.14/lisp/)]
minimal-org.el --- ;;; Minimal setup to load latest 'org-mode' ;; activate debugging (setq debug-on-error t debug-on-signal nil debug-on-quit nil) (add-to-list 'load-path "~/git-ext/org-9.1.14/lisp") (add-to-list 'load-path "~/git-ext/org-9.1.14/contrib/lisp" t) -- en minimal-org.el -- minimal file where the bug happens --- *sdfsd* *aezraze* /titi/ - end minimal file where the bug happens - Le 13/11/2018 à 17:45, Nicolas Goaziou a écrit : > Hello, > > boris martin writes: > >> since i have updated org mode to this version if i open a org-mode file >> it will not be fontify i will need to go to org->refresh/Reload->refresh >> setup current buffer >> >> to have the buffer fontify. >> >> this happen with emacs -Q -l /path/to/minimal-org.el >> as well. > I cannot reproduce it. Could you send a minimal Org file where that > happens? Also, what is in minimal-org.el? > > Regards, >
[O] LaTeX chunk makes .org file not in Org mode
Hello. I guess this is normal, but I wanted to report it in case there is room for improvement: After inserting a latex file into an .org file, I ended up with the following part in the org file (which was an agenda file): %%% Local Variables: %%% mode: latex %%% TeX-master: t %%% End: Editing this file as an org file (in Org mode), as well as agenda operations, worked well for weeks until I had to restart emacs. It was then not instantaneous to me to find out why, suddenly, 'C-c a a' failed, whereas I had not changed anything... (with message: "Agenda file xxx.org is not in Org mode") It the issue could somehow be made apparent to the user right away (that is, when the chunk is inserted), it would be easier/faster to fix. Regards -- EOST (École et Observatoire des Sciences de la Terre) IPG (Institut de Physique du Globe) | alain.coch...@unistra.fr 5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44 F-67084 Strasbourg Cedex, France| Fax: +33 (0)3 68 85 01 25
Re: [O] Org mode fontification broken
Problem solved! I had forgotten that I was using a copy of the Org repository instead of the package bundled with Emacs. Peter. On Mon, 12 Nov 2018, at 14:52, Peter Westlake wrote: > Since upgrading from Fedora 27 to Fedora 28, Emacs 26.1-3.fc28.x86_64, > links and other fontified text in Org files appear as the underlying > plain text. A few of them look correct, and deleting a marker character > (e.g. square bracket) and reinserting it makes the link appear correctly > for a while. The Messages buffer is full of things like this: > > Error during redisplay: (jit-lock-function 501) signaled (wrong-type- > argument listp org-level-4) > Error during redisplay: (jit-lock-function 1001) signaled (wrong-type- > argument listp org-level-4) > Error during redisplay: (jit-lock-function 1501) signaled (wrong-type- > argument listp org-level-3) > Error during redisplay: (jit-lock-function 2001) signaled (wrong-type- > argument listp org-level-3) > Error during redisplay: (jit-lock-function 1152403) signaled (wrong- > type-argument listp org-level-2) > > I've attempted to set jit-lock-mode to nil in .emacs, with no success. > > This Emacs has a built-in version of Org, 9.1.14, and I've tried > 20181125 installed through Melpa. Nothing makes a difference. > > Any ideas? > > Peter. >
