Feature request
https://emacs.stackexchange.com/questions/62761/seeing-file-names-in-todo-entries-when-using-org-attach?noredirect=1#comment98901_62761 ---
Error with org-update-dblock
Hello, After logging some clock time, I used the normal key combination, C-u C-c C-x C-u to update my timesheet tables, and received this error message. org-update-dblock: Symbol’s function definition is void: org-dblock-write:CLOCKTABLE This message is returned also from manually calling the function. Org mode version 9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/) GNU Emacs 27.1 (build 1, x86_64-suse-linux-gnu, GTK+ Version 3.24.22, cairo version 1.16.0) Well, after recovering from my horror at losing my timesheets for a day's work, I was able to track down the problem: the function is case sensitive. At some point, (apparently) I fat-fingered a key combo & upcased the mode line for two tables. After returning them to l-case, all worked as it should. I dunno - should the function be case insensitive? I love this tool. Now that my pulse has returned to normal. Once, it even saved me from unpleasant interviews in my manager's office. Thanks. mp "Do not neglect to do good, and to share what you have." - Hebrews 13:16a Michael Powe Naugatuck CT USA po...@ctpowe.net 503.502.9582 mobile 203.490.6447 skype
[PATCH] ox-latex.el: fix interpretation of org-latex-pdf-process
Hi all,
it seems that the documentation and code for `org-latex-pdf-process' are
out of sync: Where the documentation mentions "%bib" the code expects
"%bibtex". At least, that's how i understand it.
I resolved that confusing situation by making "%bib" and "%bibtex"
equally accepted, without touching the documentation. Thus, old
configurations work again ("%bib") as well as workarounds (using
"%bibtex") which might have gotten employed somewhere.
Cheers, Tara
From 0550f85f733bf81af7d365e81bbd7c1f22e98209 Mon Sep 17 00:00:00 2001
From: Tara Lorenz
Date: Fri, 15 Jan 2021 16:47:39 +0100
Subject: [PATCH] ox-latex.el: fix interpretation of org-latex-pdf-process
* ox-latex.el (org-latex-export-to-pdf): The documentation for
`org-latex-pdf-process' states that "%bib" will be expanded into the
current binding of `org-latex-bibtex-compiler'. However, the
`org-latex-export-to-pdf', where the expansion takes place, expects
"%bibtex" instead. This fix will accept "%bib" as well as "%bibtex"
as markers for `org-latex-bib-compiler'.
---
lisp/ox-latex.el | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index fb9fc3cd6..3b7e67844 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -3666,12 +3666,12 @@ produced."
(match-string 0)))
"pdflatex"))
(process (if (functionp org-latex-pdf-process) org-latex-pdf-process
- ;; Replace "%latex" and "%bibtex" with,
+ ;; Replace "%latex", "%bib" and "%bibtex" with,
;; respectively, "%L" and "%B" so as to adhere to
;; `format-spec' specifications.
(mapcar (lambda (command)
(replace-regexp-in-string
- "%\\(?:bib\\|la\\)tex\\>"
+ "%\\(?:\\(?:bib\\|la\\)tex\\|bib\\)\\>"
(lambda (m) (upcase (substring m 0 2)))
command))
org-latex-pdf-process)))
--
2.30.0
signature.asc
Description: PGP signature
Re: na=\"nil\" in ob-R.elo
> On Jan 14, 2021, at 3:42 PM, Brett Presnell wrote: > > > Probably a silly question, but in ob-R.el, what is the reason for > setting na=\"nil\" when defining org-babel-R-write-object-command? Is > this an elisp compatibility thing? > I don't get it either. The value corresponding to the NA becomes a string in emacs-lisp whether \"nil\" or \"\" is used. So when passed to elisp via a :post header referencing an emacs-lisp src block, its treated as a string. > Regardless, I generally (always?) want na=\"\" for this, so I am finding > all those "nil"s very annoying, and the only way that I see to defeat > them is to redefine org-babel-R-write-object-command. > > If there is no reason for the current behavior (doubtful I know) and if > I am not missing an obvious work-around, then I would like to suggest > changing this behavior. Otherwise, would it be feasible to add an > option for R code blocks (:nastring?) where one could specify the NA > replacement string? > > What do you think? It's easy to suggest I know and certainly beyond my > elisp coding skills at present, but I am supposing that someone more > fluent in elisp could do this safely without too much trouble. > You can use a :post header to customize outputs like this to make them more pleasing. Or just use your own `org-babel-R-write-object-command'. Adding another header arg qualifies as feature creep and in this case would require non-trivial work to implement. HTH, Chuck
Re: Bug: Unexpected movement of cursor when commenting code blocks
On 15 January 2021 19:48, Sébastien Miquel wrote: > I have previously proposed a patch that I think fixes this issue, see > > https://orgmode.org/list/3072e244-4615-aaad-4019-621bb3d1d...@posteo.eu/#t I applied the patch and it the problem seems to be fixed. Thank you! -- yoctocell 8B88 2502 31D7 03B1 68BC 2691 3851 020D 7E61 BBC2
bug#45091: 27.1; M-x org-table-paste-rectangle
> Okay, your bisect scripts points to one of my commits. > > But I wish it was more automated. Because I tried quite > hard and sometimes I _could_ reproduce the problem and > sometimes I couldn't. So you could be seeing noise here. > Maybe you can make your script do those copy-paste > operations automatically and reliably? Then we'd be sure. > > Anyway, I think is might be enough to point to a bug > that was introduced by my commit, or rather exposed > by it. I'll have another look. Sorry, you're true. I try to build (semi-)automatically reproduce step and do bisect with it, I got different commit. It is 165f7383822086d465519ebe6e4283723923f097 (Update Org to 9.3). (I wanted to reproduce the problem completely in auto, but the problem is related to Emacs font-lock and post-command-hook, and I could not reproduce it with --batch. If you know how to partially pass control to Emacs main-loop while running Elisp, please tell me that.) ## Repro step 1. Prepare below contents. ```latex <~/dev/tmp/taks-file.tex> -*- mode: latex -*- | rownames| acq | | ref-coal-krt-2000-4-s1@4104 | 4104 | | ref-coal-krt-2000-4-s1@4105 | 4105 | |+++---+-+-+-+--+--| || 12C12C | 12C14N | 12C14Nz12C12C | d13Cion | d15Nion | N/C | d13C | d15N | |+++---+-+-+-+--+--| | !cniso-mtx-ogl1-2@4112 ||| | | | | | | | cniso-mtx-ogl1-2@4113 ||| | | | | | | | cniso-mtx-ogl1-2@4114 ||| | | | | | | | cniso-mtx-ogl1-2@4115 ||| | | | | | | | cniso-mtx-ogl1-2@4116 ||| | | | | | | | cniso-mtx-ogl1-2@4117 ||| | | | | | | | cniso-mtx-ogl1-2@4118 ||| | | | | | | | cniso-mtx-ogl1-2@4119 ||| | | | | | | | cniso-mtx-ogl1-2@4124 ||| | | | | | | | cniso-mtx-ogl1-2@4125 ||| | | | | | | | cniso-mtx-ogl1-2@4126 ||| | | | | | | | cniso-mtx-ogl1-2@4127 ||| | | | | | | | cniso-mtx-ogl1-2@4128 ||| | | | | | | | cniso-mtx-ogl1-2@4129 ||| | | | | | | | cniso-mtx-ogl1-2@4130 ||| | | | | | | | cniso-mtx-ogl1-2@4131 ||| | | | | | | | cniso-mtx-ogl1-2@4132 ||| | | | | | | | cniso-mtx-ogl1-2@4133 ||| | | | | | | | cniso-mtx-ogl1-2@4134 ||| | | | | | | | cniso-mtx-ogl1-2@4135 ||| | | | | | | | cniso-mtx-ogl1-2@4136 ||| | | | | | | |+++---+-+-+-+--+--| ``` ```sh <~/dev/tmp/bisect-script.sh> git clean -fdx make clean ./autogen.sh ./configure --prefix=$HOME/.local/head make -j6 ./src/emacs -Q ~/dev/tmp/taks-file.tex --eval " (progn (setq truncate-lines t) (setq debug-on-error t) (require 'org) (require 'org-table) (orgtbl-mode) (search-forward \"|\") (org-table-copy-region (1+ (org-table-begin)) (- (org-table-end) 2)) (search-forward \"!\") (global-set-key (kbd \"\") (lambda () (interactive) (org-table-paste-rectangle) (set-buffer-modified-p nil) (condition-case e (insert \"text\") (error (kill-emacs 1))) (kill-emacs 0))) )" \ 2>/dev/null ``` 2. Do below command in terminal ```sh git bisect start emacs-27.1 emacs-26.3 git bisect run ~/dev/tmp/bisect-script.sh ``` 3. Wait for build and wake Emacs, then press . 4. Got commit it has some problem. (I got bellow bisect log in Magit) ``` Bisect Log (15) git bisect start 'emacs-27.1' 'emacs-26.3' git bisect good 38564f8a664347c42f7614d9c91e0d49e4a073e8 git bisect good 825fd4d34165e5edc718a9df93838a410d25ea81 git bisect good 5c5c1b559313d06aab6516ff1b1acf1da3a01c7d git bisect bad d7cd4ab7d948427104003f1d35cf52a4eac45d0a gi
Re: Bug: Unexpected movement of cursor when commenting code blocks
Hi, yoctocell writes: When I am inside a code block like this: and I hit "C-x C-;" to comment the line, the cursor automatically jumps to the second line of the code block after the comment is made. I would expect the cursor to move forward one line like it usually does and this only happens in Org-mode, not when I edit the code block in a separate buffer with "C-c C-'". I have previously proposed a patch that I think fixes this issue, see https://orgmode.org/list/3072e244-4615-aaad-4019-621bb3d1d...@posteo.eu/#t Regards, -- Sébastien Miquel
Re: How to use `open` to handle `message:*` links on macOS
Hello Tim, Tim Visher writes: > [...] > I'd like to be able to whack `C-c C-o` on `message:*` links on macOS and > have it call `open` on the contents. Is there a way to make that happen? > > My intent is to be able to save a deep link to a Mail.app message in an org > document. > [...] In my setup, I'm using this: Begin Quote - (org-add-link-type "mac-mail" 'org-mac-mail-link-open) (defun org-mac-mail-link-open (mid) "Visit the email message with message id MID." (start-process "open-mail" nil "open" (format "message:%%3C%s%%3E" mid))) - End Quote -- It gives me a new link type "mac-mail" for org-insert-link. Copy the message ID (without the angle brackets) from Mail.app, and insert it as the link location. This is a manual process, of course, but then I'm not using it often, and I don't need it for anything else but Mail.app. org-mac-link as suggested by Diego offers much more convenience by automating the entire process, and by giving you access to many other apps, too. So you might prefer that if you are going to use it often. Hoping to have helped, --alex
bug#45091: 27.1; M-x org-table-paste-rectangle
Okay, your bisect scripts points to one of my commits. But I wish it was more automated. Because I tried quite hard and sometimes I _could_ reproduce the problem and sometimes I couldn't. So you could be seeing noise here. Maybe you can make your script do those copy-paste operations automatically and reliably? Then we'd be sure. Anyway, I think is might be enough to point to a bug that was introduced by my commit, or rather exposed by it. I'll have another look. João On Fri, Jan 15, 2021 at 12:11 PM Naoya Yamashita wrote: > > > Hi, I'm new on this thread, but I can reproduce tak's issue and I > tried to do bisect. > > Finally, I got 5b45c269cda09fe46e110adb6f6767040f4ade59 is a > commit has a some problem. > > I'm happy if this information could help you. > > ``` > 5b45c269cda09fe46e110adb6f6767040f4ade59 > New jit-lock-antiblink-grace feature > > * lisp/jit-lock.el (jit-lock-antiblink-grace): New defcustom. > (jit-lock--antiblink-line-beginning-position) > (jit-lock--antiblink-string-or-comment): New variables > (jit-lock--antiblink-post-command): New helper. > (jit-lock-mode): Tweak post-command-hook and > jit-lock-context-timer. > > * etc/NEWS: Mention jit-lock-antiblink-grace > > 2 files changed, 81 insertions(+), 1 deletion(-) > etc/NEWS | 7 ++ > lisp/jit-lock.el | 75 +++- > ``` > > --- > > Here is my bash script and do `C-c l` (org-table-copy-region) on > first table and `C-c ;` (org-table-paste-rectangle) on second table. > (~/dev/tmp/taks-file.tex have first tak's mention contents.) > > ```sh > make clean > ./autogen.sh > ./configure --prefix=$HOME/.local/head > make -j6 > ./src/emacs -Q ~/dev/tmp/taks-file.tex --eval " \ > (progn\ > (setq truncate-lines t) \ > (setq debug-on-error t) \ > (require 'org) \ > (require 'org-table)\ > (orgtbl-mode) \ > (global-set-key (kbd \"C-c l\") \ >(lambda () \ > (interactive) \ > (org-table-copy-region (1+ (org-table-begin)) (- (org-table-end) > 2 \ > (global-set-key (kbd \"C-c ;\") \ >(lambda () \ > (interactive) \ > (org-table-paste-rectangle)\ > (set-buffer-modified-p nil"\ > 2>/dev/null > ``` > > And here is my bisect log. > ``` > Bisect Log (14) > git bisect start 'emacs-27.1' 'emacs-26.3' > git bisect good 38564f8a664347c42f7614d9c91e0d49e4a073e8 > git bisect good 825fd4d34165e5edc718a9df93838a410d25ea81 > git bisect good 5c5c1b559313d06aab6516ff1b1acf1da3a01c7d > git bisect bad d7cd4ab7d948427104003f1d35cf52a4eac45d0a > git bisect bad 4b2c2faab83fe3b13430b837be7d450b5cd47caf > git bisect good 16ce6dbef279bda70b4d60b4d2d0aff008bfa5f7 > git bisect bad 5063e38921de8cb872965abda32bcc6fd8894532 > git bisect bad 4c933077157ba409d645f4649c8a3a8e534d53d5 > git bisect good 096be9c4541329af259273fe604dc4f8669fbd8a > git bisect bad bd95d66ae97f3dcfe73b972de935e27e434e49be > git bisect bad 5b45c269cda09fe46e110adb6f6767040f4ade59 > git bisect good 0e774d4f355b4f12a625da5ca9602d1ba876bcc1 > 5b45c269cda09fe46e110adb6f6767040f4ade59 is the first bad commit > ``` > > > -- João Távora
bug#45091: 27.1; M-x org-table-paste-rectangle
Hi, I'm new on this thread, but I can reproduce tak's issue and I tried to do bisect. Finally, I got 5b45c269cda09fe46e110adb6f6767040f4ade59 is a commit has a some problem. I'm happy if this information could help you. ``` 5b45c269cda09fe46e110adb6f6767040f4ade59 New jit-lock-antiblink-grace feature * lisp/jit-lock.el (jit-lock-antiblink-grace): New defcustom. (jit-lock--antiblink-line-beginning-position) (jit-lock--antiblink-string-or-comment): New variables (jit-lock--antiblink-post-command): New helper. (jit-lock-mode): Tweak post-command-hook and jit-lock-context-timer. * etc/NEWS: Mention jit-lock-antiblink-grace 2 files changed, 81 insertions(+), 1 deletion(-) etc/NEWS | 7 ++ lisp/jit-lock.el | 75 +++- ``` --- Here is my bash script and do `C-c l` (org-table-copy-region) on first table and `C-c ;` (org-table-paste-rectangle) on second table. (~/dev/tmp/taks-file.tex have first tak's mention contents.) ```sh make clean ./autogen.sh ./configure --prefix=$HOME/.local/head make -j6 ./src/emacs -Q ~/dev/tmp/taks-file.tex --eval " \ (progn\ (setq truncate-lines t) \ (setq debug-on-error t) \ (require 'org) \ (require 'org-table)\ (orgtbl-mode) \ (global-set-key (kbd \"C-c l\") \ (lambda () \ (interactive) \ (org-table-copy-region (1+ (org-table-begin)) (- (org-table-end) 2 \ (global-set-key (kbd \"C-c ;\") \ (lambda () \ (interactive) \ (org-table-paste-rectangle)\ (set-buffer-modified-p nil"\ 2>/dev/null ``` And here is my bisect log. ``` Bisect Log (14) git bisect start 'emacs-27.1' 'emacs-26.3' git bisect good 38564f8a664347c42f7614d9c91e0d49e4a073e8 git bisect good 825fd4d34165e5edc718a9df93838a410d25ea81 git bisect good 5c5c1b559313d06aab6516ff1b1acf1da3a01c7d git bisect bad d7cd4ab7d948427104003f1d35cf52a4eac45d0a git bisect bad 4b2c2faab83fe3b13430b837be7d450b5cd47caf git bisect good 16ce6dbef279bda70b4d60b4d2d0aff008bfa5f7 git bisect bad 5063e38921de8cb872965abda32bcc6fd8894532 git bisect bad 4c933077157ba409d645f4649c8a3a8e534d53d5 git bisect good 096be9c4541329af259273fe604dc4f8669fbd8a git bisect bad bd95d66ae97f3dcfe73b972de935e27e434e49be git bisect bad 5b45c269cda09fe46e110adb6f6767040f4ade59 git bisect good 0e774d4f355b4f12a625da5ca9602d1ba876bcc1 5b45c269cda09fe46e110adb6f6767040f4ade59 is the first bad commit ```
