[O] Breaking up long #+TBLFM line?
Hi, Is there any way to break up an overly long #+TBLFM line? Cheers, Loris -- This signature is currently under construction.
Re: [O] How to install CDLaTeX in emacs24, on Windows 7?
"vendo.li...@libero.it" writes: > Hello, I'm having trouble understanding in which directory to download > the cdlatex.el script that Mr. Dominik wrote. I'm on Windows 7, emacs > 24, my AUCTEX version is 11.88 and I also have Org-mode 8.2 and > yasnippet installed. > When I give the command M-x org-cdlatex-mode, Emacs responds "Cannot > open load file: no such file or directory, cdlatex". I've also tried > adding the following lines into my .emacs file but to no avail. > (autoload 'org-cdlatex-mode "cdlatex.el" "Enter org-cdlatex mode" > t)(add-hook 'org-mode-hook 'turn-on-org-cdlatex) > I'm not the only person experiencing this odd behavior, infact please > check this stackexchange thread: > http://emacs.stackexchange.com/questions/19614/org-cdlatex-doesnt-work. > Can someone please confirm that yasnippet and org-cdlatex-mode are not > incompatible?Do I need to download the script from ELPA as I did with > other packages? I cannot find this script in the list of packages that > come up if I type M-x list-packages. How can I fix this problem, I > really would like to use org-cdlatex-mode under Org-mode. Thanks in > advance! You can download it here: https://raw.githubusercontent.com/cdominik/cdlatex/master/cdlatex.el Add it to your load path. Hope it helps, Rasmus -- There are known knowns; there are things we know that we know
Re: [O] bug#22399: org-mode fontification
Rasmus writes: > > Kyle Meyer writes: > >>> However, it's easy enough to switch to using an org-font-lock-ensure >>> variant that avoids these issues, so I will do that (in an updated >>> patch and on Org's maint). >> >> I've attached updated patches against emacs-25. If these are applied to >> the Emacs repo, I'll backport the new font-lock-ensure alias to Org's >> maint. > > Looks good, thanks. Just checking whether on who is going to apply the patches! They don't seem to be on emacs-25 yet. Phil
Re: [O] Tables: remote reference fails with umlaut (and in other cases)
* Nick Dokos wrote: > Eric S Fraga writes: > >> On Tuesday, 19 Jan 2016 at 14:10, Karl Voit wrote: >>> >>> #+NAME: 2016-01-19-srctbl >>> | Testdata | >>> >>> |--| >>> | foobar | >>> | fooübar | >>> | fooßbar | >>> | 1er | >>> | 23,42| >>> | 23.42| >>> >>> | Result | Expected Result | Comparison | >>> |--+-+| >>> | foobar | foobar | OK | >>> | #ERROR | fooübar | fail | >>> | #ERROR | fooßbar | fail | >>> | er | 1er | fail | >>> | 23.42| 23.42 | OK | >>> | (23, 42) | 23,42 | probably fail? | >>> #+TBLFM: $1=remote(2016-01-19-srctbl,@@#$1) > > You are missing a quote: > #+TBLFM: $1='(identity remote(2016-01-19-srctbl,@@#$1)) > works for me. And this works for me as well. Thank you very much for your help! -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
[O] R: Re: How to install CDLaTeX in emacs24, on Windows 7?
Rasmus, Thank you for your suggestion. I'm not very good at emacs so when you say "load path" do you mean ? My .emacs configuration file is in , so where do I put cdlatex.el? Do you know if yasnippet and cdlatex are compatible or not?Please refer to the screenshot at this link for Emacs my path file: http://stackoverflow.com/questions/34884310/emacs-org-cdlatex-mode-where-do-you-put-the-cdlatex-el-script >Messaggio originale >Da: Rasmus >Data: 20-gen-2016 11.15 >A: >Ogg: Re: [O] How to install CDLaTeX in emacs24, on Windows 7? > >"vendo.li...@libero.it" writes: > >> Hello, I'm having trouble understanding in which directory to download >> the cdlatex.el script that Mr. Dominik wrote. I'm on Windows 7, emacs >> 24, my AUCTEX version is 11.88 and I also have Org-mode 8.2 and >> yasnippet installed. >> When I give the command M-x org-cdlatex-mode, Emacs responds "Cannot >> open load file: no such file or directory, cdlatex". I've also tried >> adding the following lines into my .emacs file but to no avail. >> (autoload 'org-cdlatex-mode "cdlatex.el" "Enter org-cdlatex mode" >> t)(add-hook 'org-mode-hook 'turn-on-org-cdlatex) >> I'm not the only person experiencing this odd behavior, infact please >> check this stackexchange thread: >> http://emacs.stackexchange.com/questions/19614/org-cdlatex-doesnt-work. >> Can someone please confirm that yasnippet and org-cdlatex-mode are not >> incompatible?Do I need to download the script from ELPA as I did with >> other packages? I cannot find this script in the list of packages that >> come up if I type M-x list-packages. How can I fix this problem, I >> really would like to use org-cdlatex-mode under Org-mode. Thanks in >> advance! > >You can download it here: > >https://raw.githubusercontent.com/cdominik/cdlatex/master/cdlatex.el > >Add it to your load path. > >Hope it helps, >Rasmus > >-- >There are known knowns; there are things we know that we know > > >
Re: [O] Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)
Hello, Derek Feichtinger writes: > org-resolve-clock loops over all open org buffers for detecting open > clocks (using function org-files-list). Is this really intended? I think > it should just loop over the org-agenda-files. > > I was working on an extension for clocking and was recording my testing > results > into a separate org file. I also had put there examples of > various clock lines to test regexps against. The example clock lines > effectively prevented me from clocking in to a task from my normal > agenda files. > > Since org has so many usages, I think it should not be assumed that each > org buffer is related to the agenda functionality. Clocking is not just an agenda functionality. Since every Org document can contain clocks, it makes sense to use `org-files-list' instead of `org-agenda-files'. You could test your extension in a dedicated Emacs process, with `org-agenda-files' being nil and Org documents opened piece-wise. Regards, -- Nicolas Goaziou
Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]
Hello, Gregor Zattler writes: > Notes produced when clocking out with org-log-note-clock-out set > will be placed above the clock line instead below the clock line. > In my heavily customized sessions the notes show up on the > previos line respective to the clock line. Without > customizations (see below) they end up above the :LOGBOOK: > drawer. > > ECM: > emacs24 -Q -nw -L /home/grfz/src/org-mode/lisp/ --eval "(require 'org)" > --eval '(setq org-log-note-clock-out t)' /tmp/test.org > > now add a heading, clock in, clock out, write something as a note, > do C-c C-c to finish note taking. Result: > > * heading > - note > :LOGBOOK: > CLOCK: [2016-01-19 Di 16:22]--[2016-01-19 Di 16:22] => 0:00 > :END: I can reproduce it. However, I don't think it is a bug. It looks like the expected default behaviour. By default, clocks and notes are not stored at the same location. See `org-log-into-drawer' and `org-clock-into-drawer'. So, there's no reason to put them together here. Moreover, I cannot see anything in the code that would make "clock notes" special in any way. This is basically the same as calling `org-add-note' right after clocking out, and, as this function's docstring points out: This is done in the same way as adding a state change note. OTOH, the manual says See the variable ‘org-log-note-clock-out’ for the possibility to record an additional note together with the clock-out timestamp. In particular, the term "together" is ambiguous, as it can indeed be understood as "at the same place". However, I doubt the intent is to create a new type of note that would purposely ignore global logging settings. So I lean towards a documentation bug here. WDYT? Regards, -- Nicolas Goaziou
[O] Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Hello When I started using GNU Emacs compiled from the emacs25 branch two issues come up consistently during Org make routine. These issues are related to changes in the next Emacs version. [...] Compiling /home/user/repositories/org-mode/lisp/org-src.el... In org-src-font-lock-fontify-block: org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead. [...] Compiling /home/user/repositories/org-mode/lisp/org.el... In org-fast-tag-selection: org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use ‘push’ or ‘cl-pushnew’ [...] Note that the .elc files get generated just fine, I mean, the make routine finishes correctly and Org is still usable.
Re: [O] How to install CDLaTeX in emacs24, on Windows 7?
"vendo.li...@libero.it" writes: > I'm not very good at emacs Don’t worry. It will come! You could check (info "eintr"); it’s a pretty cool book. > so when you say "load path" do you mean ? My > .emacs configuration file is in , so where do I put > cdlatex.el? Do you know if yasnippet and cdlatex are compatible or not? It’s configurable. Check the folders in the variable load-path (hint: do C-h v RET load-path RET; RET is Enter, C is Ctrl) Try to add something like this to your init.el: (add-to-list 'load-path (expand-file-name (concat user-emacs-directory "lisp"))) And evaluate it in the session (C-x C-e at last closing parenthesis). Then look up the value of load-path. It will probably be something like C:\home\.emacs.d\lisp (I don’t know windows very well, sorry). Now put the cdlatex.el in this folder. It’s now in the Emacs load path and you, or Org, can require it. If you want to be fancy, you can byte-compile cdlatex.el (M-x byte-compile-file). > Please refer to the screenshot at this > link for Emacs my path file: > http://stackoverflow.com/questions/34884310/emacs-org-cdlatex-mode-where-do-you-put-the-cdlatex-el-script I did not check this. Hope it helps, Rasmus -- The right to be left alone is a human right
Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]
Hi Nicolas, * Nicolas Goaziou [20. Jan. 2016]: > Gregor Zattler writes: >> Notes produced when clocking out with org-log-note-clock-out set >> will be placed above the clock line instead below the clock line. >> In my heavily customized sessions the notes show up on the >> previos line respective to the clock line. Without >> customizations (see below) they end up above the :LOGBOOK: >> drawer. >> >> ECM: >> emacs24 -Q -nw -L /home/grfz/src/org-mode/lisp/ --eval "(require 'org)" >> --eval '(setq org-log-note-clock-out t)' /tmp/test.org >> >> now add a heading, clock in, clock out, write something as a note, >> do C-c C-c to finish note taking. Result: >> >> * heading >> - note >> :LOGBOOK: >> CLOCK: [2016-01-19 Di 16:22]--[2016-01-19 Di 16:22] => 0:00 >> :END: > > I can reproduce it. However, I don't think it is a bug. It looks like > the expected default behaviour. > > By default, clocks and notes are not stored at the same location. See > `org-log-into-drawer' and `org-clock-into-drawer'. So, there's no reason > to put them together here. > > Moreover, I cannot see anything in the code that would make "clock > notes" special in any way. This is basically the same as calling > `org-add-note' right after clocking out, and, as this function's > docstring points out: > > This is done in the same way as adding a state change note. > > OTOH, the manual says > > See the variable ‘org-log-note-clock-out’ for the possibility to > record an additional note together with the clock-out timestamp. > > In particular, the term "together" is ambiguous, as it can indeed be > understood as "at the same place". However, I doubt the intent is to > create a new type of note that would purposely ignore global logging > settings. So I lean towards a documentation bug here. > > WDYT? Thanks for your explanation. To me this is not a documentation bug. What the documentation describes allows for a helpful distinction of notes in different contexts which IMHO should not be conflated: I understand that to you all notes are created equal: They somehow belong to a node. I think the note taken when clocking out belongs specifically to its clock line and explains it. Clocking is for reasons of measurement of time often in context of accounting. Such notes answer to the question ""Why took it so long". This is different to notes which are there to remember specific aspects of a tasks. This was default behaviour when users decided to be asked for a note taken after clocking out. I for instance document my working hours this way and have 2072 such notes sitting below their corresponding clock line. I have the task of maintaining some complex spreadsheets for the accounting department. My employer want's to know how much time I spend on this task. So I clock this working hours. I want to be able to anser to the question why it took so long. OTHT there are notes regarding the work with these complex spreadsheets, e.g. "conditional colouring of cells may lead to performance problem when thousands of conditionally coloured cells are in use". This is a note which belongs to the Spreadsheets and is not only true for the time interval indicated by a clock line. It would be great when notes taken when clocking out would come next to their respective clock lines. Thanks for your attention, Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: [O] Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Hi Vicente, Vicente Vera writes: > Hello > > When I started using GNU Emacs compiled from the emacs25 branch two > issues come up consistently during Org make routine. These issues are > related to changes in the next Emacs version. Thanks for reporting these. > Compiling /home/user/repositories/org-mode/lisp/org-src.el... > > In org-src-font-lock-fontify-block: > org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use > only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead. This has been switched over to font-lock-ensure a couple times (in f36b19e and then reverted in 99f, then again in d81e6b5 and reverted in 003a0f1). When font-lock-ensure is used, source blocks don't get highlighted. > Compiling /home/user/repositories/org-mode/lisp/org.el... > > In org-fast-tag-selection: > org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use > ‘push’ or ‘cl-pushnew’ I think this one should be fixed. I'll look into it. -- Kyle
Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]
Gregor Zattler writes: > Thanks for your explanation. To me this is not a documentation > bug. What the documentation describes allows for a helpful > distinction of notes in different contexts which IMHO should not > be conflated: > > I understand that to you all notes are created equal: They > somehow belong to a node. > > I think the note taken when clocking out belongs specifically to > its clock line and explains it. Clocking is for reasons of > measurement of time often in context of accounting. Such notes > answer to the question ""Why took it so long". This is different > to notes which are there to remember specific aspects of a tasks. > > This was default behaviour when users decided to be asked for a > note taken after clocking out. > > I for instance document my working hours this way and have > 2072 such notes sitting below their corresponding clock > line. > > I have the task of maintaining some complex spreadsheets for > the accounting department. My employer want's to know how > much time I spend on this task. So I clock this working > hours. I want to be able to anser to the question why it > took so long. > > OTHT there are notes regarding the work with these complex > spreadsheets, e.g. "conditional colouring of cells may lead > to performance problem when thousands of conditionally > coloured cells are in use". This is a note which belongs to > the Spreadsheets and is not only true for the time interval > indicated by a clock line. > > It would be great when notes taken when clocking out would come > next to their respective clock lines. This is already possible: just make sure notes and clocks are stored at the same location (e.g., set `org-log-into-drawer' to t in your ECM). However, by default, they aren't. I see no reason to force notes taken upon clocking out to be always located next to the clock line, as long as you can get that behaviour somehow. Thus, I think the documentation could be improved as it sort of implies clock notes are always next to the closed clock. IIUC, you are suggesting to implement two types of notes, but that never was the case in Org, AFAICT. You could, however, use a hook (e.g., `org-clock-out-hook') in order to put data relative to clocks in a specific drawer and keep general notes in LOGBOOK at the same time. Regards, -- Nicolas
[O] R: Re: How to install CDLaTeX in emacs24, on Windows 7?
Hello Rasmus, I did as you told me and finally CDLaTeX works in Org mode! The command C-h v RET load-path RET revealed I had many load-paths, among them: "c:/home/.emacs.d/elpa/auctex-11.88.8/" "c:/Program Files/emacs-24.4/share/emacs/site-lisp" "c:/Program Files/emacs-24.4/share/emacs/24.4/lisp" "c:/Program Files/emacs-24.4/share/emacs/24.4/lisp/org" ...just to name a few! I inserted it in "c:/Program Files/emacs-24.4 /share/emacs/24.4/lisp", restarted the machine and tried it out on an *.org file. It immediately recognized it! However I now have a new problem -- when I enable CDLaTeX the backtick doesn't work! This is really annoying since many commands of CDLaTeX absolutely need the backtick symbol, ( ` ). When I press the key while in CDLaTeX mode, emacs says "Wrong type argument: characterp, 134217782". But if I disable CDLaTeX and press that key again, Org gives no problem and prints it on screen. I should point out that I use Colemak keyboard layout (not sure if it's relevant) and I have redefined the backtick key and the tilde (Shift+backtick) in my .emacs configuration file, in the following way: ;;; a key for tilde symbol (define-key key-translation-map (kbd "M-2") (kbd "~")) ;;; a key for backtick symbol (define-key key-translation-map (kbd "M-6") "") (define-key key-translation-map (kbd "M-9") (kbd "`")) I suppose I must find a way to tell CDLaTeX that that key is backtick and it should accept it in order to execute the commands I'm typing. How do say that in e-lisp? >Messaggio originale >Da: Rasmus >Data: 20-gen-2016 15.25 >A: >Ogg: Re: [O] How to install CDLaTeX in emacs24, on Windows 7? > >"vendo.li...@libero.it" writes: > >> I'm not very good at emacs > >Don’t worry. It will come! > >You could check (info "eintr"); it’s a pretty cool book. > >> so when you say "load path" do you mean ? My >> .emacs configuration file is in , so where do I put >> cdlatex.el? Do you know if yasnippet and cdlatex are compatible or not? > >It’s configurable. Check the folders in the variable load-path >(hint: do C-h v RET load-path RET; RET is Enter, C is Ctrl) > >Try to add something like this to your init.el: > >(add-to-list 'load-path (expand-file-name > (concat user-emacs-directory "lisp"))) > >And evaluate it in the session (C-x C-e at last closing parenthesis). >Then look up the value of load-path. It will probably be something like >C:\home\.emacs.d\lisp (I don’t know windows very well, sorry). Now put >the cdlatex.el in this folder. It’s now in the Emacs load path and you, >or Org, can require it. If you want to be fancy, you can byte-compile >cdlatex.el (M-x byte-compile-file). > >> Please refer to the screenshot at this >> link for Emacs my path file: >> http://stackoverflow.com/questions/34884310/emacs-org-cdlatex-mode-where-do- you-put-the-cdlatex-el-script > >I did not check this. > >Hope it helps, >Rasmus > >-- >The right to be left alone is a human right > > >
[O] bug#22399: org-mode fontification
phillip.l...@russet.org.uk (Phillip Lord) writes: > Rasmus writes: >> >> Kyle Meyer writes: >> However, it's easy enough to switch to using an org-font-lock-ensure variant that avoids these issues, so I will do that (in an updated patch and on Org's maint). >>> >>> I've attached updated patches against emacs-25. If these are applied to >>> the Emacs repo, I'll backport the new font-lock-ensure alias to Org's >>> maint. >> >> Looks good, thanks. > > > Just checking whether on who is going to apply the patches! They don't > seem to be on emacs-25 yet. I have copyright assignment with the FSF (for Org mode contributions), but I haven't contributed to Emacs directly before. I'm cc'ing Stefan because these patches are touching his changes. I've re-attached the most recent set of patches (http://permalink.gmane.org/gmane.emacs.bugs/111756). >From d9a8014e3919c328bf2b6acbe9d9127f3b06b5e1 Mon Sep 17 00:00:00 2001 From: Kyle Meyer Date: Tue, 19 Jan 2016 12:53:04 -0500 Subject: [PATCH 1/2] org-compat: Fix font-lock-ensure alias * lisp/org/org-compat.el (org-font-lock-ensure): Fix check for font-lock-ensure. Make compatibility function's arguments optional to match with font-lock-ensure's. (Bug#22399) --- lisp/org/org-compat.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org/org-compat.el b/lisp/org/org-compat.el index 6403d4d..cf6aafc 100644 --- a/lisp/org/org-compat.el +++ b/lisp/org/org-compat.el @@ -479,9 +479,9 @@ org-no-popups (not (null pos) (defalias 'org-font-lock-ensure - (if (fboundp 'org-font-lock-ensure) + (if (fboundp 'font-lock-ensure) #'font-lock-ensure -(lambda (_beg _end) (font-lock-fontify-buffer +(lambda (&optional _beg _end) (font-lock-fontify-buffer (defun org-floor* (x &optional y) "Return a list of the floor of X and the fractional part of X. -- 2.7.0 >From 7b2e8cd23ee5326ca2b0845bed8a5d111a2a3b17 Mon Sep 17 00:00:00 2001 From: Kyle Meyer Date: Tue, 19 Jan 2016 12:53:22 -0500 Subject: [PATCH 2/2] org-src: Use font-lock-fontify-buffer for blocks * lisp/org/org-src.el (org-src-font-lock-fontify-block): Use font-lock-fontify-buffer because font-lock-ensure does not display source block fonts. This corresponds to 003a0f10695f035e844d844eacb1a86a6d2df934 in the Org repo. --- lisp/org/org-src.el | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lisp/org/org-src.el b/lisp/org/org-src.el index 8e06aaa..5548f52 100644 --- a/lisp/org/org-src.el +++ b/lisp/org/org-src.el @@ -916,7 +916,9 @@ org-src-font-lock-fontify-block (delete-region (point-min) (point-max)) (insert string " ") ;; so there's a final property change (unless (eq major-mode lang-mode) (funcall lang-mode)) -(org-font-lock-ensure) + ;; Avoid `font-lock-ensure', which does not display fonts in + ;; source block. + (font-lock-fontify-buffer) (setq pos (point-min)) (while (setq next (next-single-property-change pos 'face)) (put-text-property -- 2.7.0 -- Kyle
Re: [O] Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Hello Kyle, Thanks for your reply. I see now why `font-lock-fontify-buffer' hasn't been replaced. 2016-01-20 12:28 GMT-03:00 Kyle Meyer : > Hi Vicente, > > Vicente Vera writes: > >> Hello >> >> When I started using GNU Emacs compiled from the emacs25 branch two >> issues come up consistently during Org make routine. These issues are >> related to changes in the next Emacs version. > > Thanks for reporting these. > >> Compiling /home/user/repositories/org-mode/lisp/org-src.el... >> >> In org-src-font-lock-fontify-block: >> org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use >> only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead. > > This has been switched over to font-lock-ensure a couple times (in > f36b19e and then reverted in 99f, then again in d81e6b5 and reverted > in 003a0f1). When font-lock-ensure is used, source blocks don't get > highlighted. > >> Compiling /home/user/repositories/org-mode/lisp/org.el... >> >> In org-fast-tag-selection: >> org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use >> ‘push’ or ‘cl-pushnew’ > > I think this one should be fixed. I'll look into it. > > -- > Kyle
[O] bug#22399: org-mode fontification
> (defalias 'org-font-lock-ensure > - (if (fboundp 'org-font-lock-ensure) > + (if (fboundp 'font-lock-ensure) >#'font-lock-ensure > -(lambda (_beg _end) (font-lock-fontify-buffer > +(lambda (&optional _beg _end) (font-lock-fontify-buffer Looks good. > (unless (eq major-mode lang-mode) (funcall lang-mode)) > -(org-font-lock-ensure) > + ;; Avoid `font-lock-ensure', which does not display fonts in > + ;; source block. > + (font-lock-fontify-buffer) Intuitively, this looks like a wrong fix. Do you have a reproducible recipe showing the problem that you're trying to fix? Stefan
Re: [O] Bug: org-map-entries seems broken
Hello, Thank you so much for looking into this. Kyle Meyer writes: >> Hello, >> >> I have a function that uses org-map-entries to build a list of entries. [... 6 lines omitted ...] > > Things seem to be working on my end. Both release_8.3.3 and the > current master (23f31a9) are giving me the same results: [... 36 lines omitted ...] The problem, which took me several hours to figure out, was merely a massive misfire between my keyboard and chair. I apologize for the noise. Best, Terry
[O] Bug: Column view next allowed value throws error
Hello all, With the most recent Org from git, attempting to change to the next or previous allowed value in Column View throws an error: Symbol's value as variable is void: pom An ECM for the error: Type =make vanilla= at the command prompt. Change the scratch buffer to org-mode. Erase the buffer and paste this instead (not including the #+...EXAMPLE lines, of course: #+BEGIN_EXAMPLE ,* Top node for columns view :PROPERTIES: :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO :END: ,** TODO This ,** TODO That #+END_EXAMPLE Move the cursor to the second heading. Press C-c C-x C-c to go to column view. Move to the P column. Press n to change the value to the next allowable value. This error appears: #+BEGIN_QUOTE Symbol's value as variable is void: pom #+END_QUOTE Performing the same steps but starting with emacs -Q in Debian Testing produces the expected results, no error. Emacs : GNU Emacs 24.5.1 (i586-pc-linux-gnu, GTK+ Version 3.18.2) of 2015-10-24 on x86-grnet-01, modified by Debian Package: Org-mode version 8.3.3 (release_8.3.3-470-g3142d1.dirty @ /home/tftorrey/T/hacks/org-mode/lisp/) Thanks in advance, Terry
Re: [O] Bug: Column view next allowed value throws error
Hello, "T.F. Torrey" writes: > With the most recent Org from git, attempting to change to the next or > previous allowed value in Column View throws an error: Symbol's value as > variable is void: pom > > An ECM for the error: > > Type =make vanilla= at the command prompt. > > Change the scratch buffer to org-mode. > > Erase the buffer and paste this instead (not including the #+...EXAMPLE > lines, of course: > > #+BEGIN_EXAMPLE > ,* Top node for columns view > :PROPERTIES: > :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO > :END: > > ,** TODO This > > ,** TODO That > #+END_EXAMPLE > > Move the cursor to the second heading. > > Press C-c C-x C-c to go to column view. > > Move to the P column. > > Press n to change the value to the next allowable value. > > This error appears: > > #+BEGIN_QUOTE > Symbol's value as variable is void: pom > #+END_QUOTE Fixed. Thank you. Regards, -- Nicolas Goaziou
[O] bug#22399: org-mode fontification
Thanks for having a look. Stefan Monnier writes: >> (unless (eq major-mode lang-mode) (funcall lang-mode)) >> -(org-font-lock-ensure) >> +;; Avoid `font-lock-ensure', which does not display fonts in >> +;; source block. >> +(font-lock-fontify-buffer) > > Intuitively, this looks like a wrong fix. Do you have a reproducible > recipe showing the problem that you're trying to fix? Sure. With --8<---cut here---start->8--- #+BEGIN_SRC elisp (require 'cl-lib) (message "test") #+END_SRC --8<---cut here---end--->8--- in /tmp/scratch.org, run emacs -Q --eval "(setq org-src-fontify-natively t)" --visit /tmp/scratch.org Go to the code block and hit C-c ' (org-edit-special), and then exit with another C-c '. Without this change, the source block is no longer highlighted as elisp code when I return to the buffer. I don't think it's just something odd on my end because, when we backported 6711a21, a user reported that he lost highlighting in source blocks. http://thread.gmane.org/gmane.emacs.orgmode/99495 -- Kyle
Re: [O] Bug: [bisected] note from clocking out is above :LOGBOOK: drawer [8.3.3 (release_8.3.3-469-g2e7716 @ /home/grfz/src/org-mode/lisp/)]
Hi Nicolas, * Nicolas Goaziou [20. Jan. 2016]: > Gregor Zattler writes: >> It would be great when notes taken when clocking out would come >> next to their respective clock lines. > > This is already possible: just make sure notes and clocks are stored at > the same location (e.g., set `org-log-into-drawer' to t in your ECM). Actually this keeps all notes in the :LOGBOOK: drawer but notes taken while clocking out appear above instead of below the clock line. I would have to shuffle all existing clock-out-notes above their respective clock line in order to have consistent documents. This is doable. This way notes taken while clocked in are mixed with the ones taken when clocking out and are even nearer to the clock line. But... > However, by default, they aren't. > > I see no reason to force notes taken upon clocking out to be always > located next to the clock line, as long as you can get that behaviour > somehow. Thus, I think the documentation could be improved as it sort of > implies clock notes are always next to the closed clock. > > IIUC, you are suggesting to implement two types of notes, but that never > was the case in Org, AFAICT. You could, however, use a hook (e.g., > `org-clock-out-hook') in order to put data relative to clocks in > a specific drawer and keep general notes in LOGBOOK at the same time. ... I guess this hook will be run before actually clocking out? Thus I would change the notes drawer to the clock line drawer, clock out and set it back again? Thanks for your help, Gregor -- -... --- .-. . -.. ..--.. ...-.-
