Endnote-style bibliographic citation with Zotero, zotxt-emacs, and org-mode
I'm trying to write a book in org-mode. The book will contain numerous citations to journal articles (in addition to books or URLs), which are all stored in my Zotero library. I've successfully installed the Zotero addons zotxt & Better Bibtex for Zotero, as well as the Emacs package zotxt (zotxt-emacs). I can create the basic citation using the "@AUTHOR_FIRSTTITLEWORD_YEAR" style (set org-zotxt-link-description-style variable to :betterbibtexkey and then use C-c " i to insert references). My book being targetted to the general public, I want to use end-notes instead of the usual citation format (LastName, Year). Something like: Experts studied ([[zotero://select/items/1_VDVFUIBV][1]], [[zotero://select/items/1_TXDISZDFR][2]]) that animals behave very differently under captivity. And then all the references will go to the References chapter. Judging from reading the org-zotxt.el source code in the zotxt-emacs package (with my non-existant Emacs Lisp knowledge) I conclude that this is not supported. But I can certainly whip up some script to preprocess the Org document to change the betterbibtexkey description style to the numbers before exporting. There are also a few other things I want/need but don't know yet how to accomplish. Like generating the References chapter (will probably whip up some script again), making item searching less painful, doing something useful when a zotero Org link is opened (org-open-at-point), or customizing the ODT export (hopefully creating Zotero reference instead of just unlinked text or broken links). Anyone already using Zotero and org-mode, and in the same situation? I'm not tied to zotxt; still open to using org-ref or other alternatives; but I want to keep both org-mode and Zotero.
Re: Problem
On Saturday, 4 Apr 2020 at 13:13, Charles Millar wrote: > OK, started over. > > Please see attached backtrace and the file I used. Strange. Your example file works just fine for me. What version of org are you using? And LaTeX? Can you export to LaTeX (C-c C-e k l) and see if that LaTeX file compiles manually? -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-438-g5b9698
Re: negative values for EFFORT result in error when switching to column view
Hello, Heiko Schmidt writes: > When M-x org-columns I'd like to see column view with the balanced sum > of the hours planned and the hours really worked, but I get an error > > cond: Invalid duration format: "-2 h" > > I know I'm using old versions but this problem is also on newer > versions. Effort property accepts a specific, and well defined type of value: a duration. Such values cannot be negative, as explained in the error message. You may, however, use a different property for your use-case, and apply column view on it. Regards, -- Nicolas Goaziou
Re: Problem
On 4/6/20 4:37 AM, Eric S Fraga wrote:
On Saturday, 4 Apr 2020 at 13:13, Charles Millar wrote:
OK, started over.
Please see attached backtrace and the file I used.
Strange. Your example file works just fine for me.
What version of org are you using? And LaTeX?
Just ran the same file with the following versions
Org mode version 9.3.6 (release_9.3.6-449-gb99357 @
/usr/local/share/org-mode/lisp/)
GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version 3.24.14,
cairo version 1.16.0) of 2020-04-06
attached is the backtrace.
Can you export to LaTeX (C-c C-e k l) and see if that LaTeX file
compiles manually?
no Latex file produced.
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
format-spec(nil ((116 . #("Mis-shapen chaos of well-seeming forms!" 0 39
(:parent (#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent #7))
(97 . #("Romeo" 0 5 (:parent (#("Romeo" 0 5 (:parent #8)) (116 .
#("Mis-shapen chaos of well-seeming forms!" 0 39 (:parent (#("Mis-shapen chaos
of well-seeming forms!" 0 39 (:parent #9)) (115 . "") (107 . "") (100 . "")
(99 . "Emacs 28.0.50 (Org mode 9.3.6)") (108 . "english") (76 . "English") (68
#("1580" 0 4 (:parent #13)
(concat (if (and with-subject (not (eq with-subject t))) (progn (format
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template
spec) "\\begin{document}\n\n" (if subject (progn (format
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title)
(org-string-nw-p subject)) (progn "\n")))
(let* ((with-subject (plist-get info :with-subject)) (with-title (plist-get
info :with-title)) (title-as-subject (and with-subject (plist-get info
:with-title-as-subject))) (subject* (org-string-nw-p (org-export-data
(plist-get info :subject) info))) (title* (and with-title (org-string-nw-p
(org-export-data (plist-get info :title) info (subject (cond ((not
with-subject) nil) (title-as-subject (or subject* title*)) (t subject*)))
(title (cond ((not with-title) nil) (title-as-subject (and subject* title*)) (t
title*))) (hyperref-template (plist-get info :latex-hyperref-template)) (spec
(append (list (cons 116 (or title subject ""))) (org-latex--format-spec
info (concat (if (and with-subject (not (eq with-subject t))) (progn
(format "\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject
(mapconcat #'symbol-name with-subject ",") (format-spec hyperref-template
spec) "\\begin{document}\n\n" (if subject (progn (format
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title)
(org-string-nw-p subject)) (progn "\n"
(concat (and (plist-get info :time-stamp-file) (format-time-string "%%
Created %Y-%m-%d %a %H:%M\n")) (org-latex--insert-compiler info)
(org-latex-make-preamble info) (org-koma-letter--build-settings 'global info)
(mapconcat #'(lambda (file) (format "\\LoadLetterOption{%s}\n" file))
(split-string (or (plist-get info :lco) "")) "")
(org-koma-letter--build-settings 'buffer info) (format "\\date{%s}\n"
(org-export-data (org-export-get-date info) info)) (let* ((with-subject
(plist-get info :with-subject)) (with-title (plist-get info :with-title))
(title-as-subject (and with-subject (plist-get info :with-title-as-subject)))
(subject* (org-string-nw-p (org-export-data (plist-get info :subject) info)))
(title* (and with-title (org-string-nw-p (org-export-data (plist-get info
:title) info (subject (cond ((not with-subject) nil) (title-as-subject (or
subject* title*)) (t subject*))) (title (cond ((not with-title) nil)
(title-as-subject (and subject* title*)) (t title*))) (hyperref-template
(plist-get info :latex-hyperref-template)) (spec (append (list (cons 116 (or
title subject ""))) (org-latex--format-spec info (concat (if (and
with-subject (not (eq with-subject t))) (progn (format
"\\KOMAoption{subject}{%s}\n" (if (symbolp with-subject) with-subject
(mapconcat ... with-subject ",") (format-spec hyperref-template spec)
"\\begin{document}\n\n" (if subject (progn (format
"\\setkomavar{subject}{%s}\n" subject))) (if title (progn (format
"\\setkomavar{title}{%s}\n" title))) (if (or (org-string-nw-p title)
(org-string-nw-p subject)) (progn "\n" (let ((keyword-val (plist-get info
:to-address)) (heading-val (org-koma-letter--get-tagged-contents 'to))) (format
"\\begin{letter}{%%\n%s}\n\n" (org-koma-letter--add-latex-newlines (or (if
(plist-get info :special-headings) (or heading-val keyword-val) (or keyword-val
heading-val)) "\\mbox{}" (format "\\opening{%s}\n\n"
(org-koma-letter--keyword-or-headline :opening #'(lambda (h i) (not
(org-koma-letter--special-tag h i))) info)) contents (format "\\closing{%s}\n"
(org-koma-letter--keyword-or-headline :closing #'(lambda (h i) (let
((special-t
Re: Problem
On Monday, 6 Apr 2020 at 07:49, Charles Millar wrote: > Just ran the same file with the following versions > > Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ > /usr/local/share/org-mode/lisp/) > GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version > 3.24.14, cairo version 1.16.0) of 2020-04-06 okay, one less variable. have you tried this with "emacs -Q" in case there's something in your configuration? -- : Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-438-g5b9698
Re: Problem
Hello, Eric S Fraga writes: > On Monday, 6 Apr 2020 at 07:49, Charles Millar wrote: >> Just ran the same file with the following versions >> >> Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ >> /usr/local/share/org-mode/lisp/) >> GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version >> 3.24.14, cairo version 1.16.0) of 2020-04-06 > > okay, one less variable. > > have you tried this with "emacs -Q" in case there's something in your > configuration? This happens because `org-latex-hyperref-template' is empty, which is a valid use-case. I fixed it in both maint and master. Thanks to you two for the report and the debugging help. Regards, -- Nicolas Goaziou
Re: Do something useful with ".+" and hours repeaters
Hello, Kyle Meyer writes: > You could use floor's DIVISOR argument: > > (floor (- (org-time-stamp-to-now ts t)) 60) Good catch! I keep forgetting about this argument. I added tests, mentioned the change in ORG-NEWS, and applied the patch. I hesitated using the UPDOWN optional argument from `org-timestamp-change' (i.e., obey to `org-time-stamp-rounding-minutes'), but eventually decided to ignore it for now. We can always reconsider this later on. Thank you. Regards, -- Nicolas Goaziou
Re: Bug: org-agenda-tag-filter-preset not respected [9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/jorge/.config/emacs/elpa/27.0/develop/org-plus-contrib-20200302/)]
Em [2020-03-09 seg 20:36:33-0300], Jorge P. de Morais Neto escreveu: > Em [2020-03-06 sex 09:06:35-0300], Jorge P. de Morais Neto escreveu: > >> Hi. Since version org-plus-contrib-20200302, my agenda is buggy. The >> bug did not occur in previous versions. > > Actually, I realized the bug occurs since org-plus-contrib-20200224. Hi. I am sorry for insisting, but this bug report is a month old and has not been added to <https://orgmode.org/worg/org-issues.html>. I have just tested and reproduced it with Emacs 27 -- emacs-27 branch, snapshot from [2020-04-04 sáb] -- and org-plus-contrib 20200406. In this situation, is it OK to remind you of the bug every month? I honestly do not know the netiquette about this. Regards -- - <https://jorgemorais.gitlab.io/justice-for-rms/> - I am Brazilian. I hope my English is correct and I welcome feedback. - <https://www.defectivebydesign.org/> - <https://www.gnu.org/>
Re: Problem
On 4/6/20 8:33 AM, Nicolas Goaziou wrote: Hello, Eric S Fraga writes: On Monday, 6 Apr 2020 at 07:49, Charles Millar wrote: Just ran the same file with the following versions Org mode version 9.3.6 (release_9.3.6-449-gb99357 @ /usr/local/share/org-mode/lisp/) GNU Emacs 28.0.50 (build 87, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, cairo version 1.16.0) of 2020-04-06 okay, one less variable. have you tried this with "emacs -Q" in case there's something in your configuration? This happens because `org-latex-hyperref-template' is empty, which is a valid use-case. I fixed it in both maint and master. Thanks to you two for the report and the debugging help. Regards, Downloaded and installed Org mode version 9.3.6 (release_9.3.6-454-g3c87b8 @ /usr/local/share/org-mode/lisp/) and I confirm that I have now produce the letter to Juliet using ox-koma-letter. BTW, it matches the Worg example-pdf. Thank you Eric and everyone else, who have guided me. Charlie Millar
Re: negative values for EFFORT result in error when switching to column view
On 06.04.20 12:13, Nicolas Goaziou wrote: Effort property accepts a specific, and well defined type of value: a duration. Such values cannot be negative, as explained in the error message. You may, however, use a different property for your use-case, and apply column view on it. Regards, This is exactly the reason why I'd love to have negative values for the durations. It would open the possibility of doing something like "accounting" of time. I'm working with self defined duration units and it would be of great value to be able to calculate the balance for planned and done work time. I don't use clocking. What'd be wrong about having -0:30 h, -30 min, -2.5 h, -3 d or -3 m? It'd be an addition no change so there would hoefully be no incompatibilities. Maybe even 3m -3d be or -3m 3d could be of use. As I see there is org-duration.el - Have the changes to be made only there? Best Regards
Re: negative values for EFFORT result in error when switching to column view
Heiko Schmidt writes: > This is exactly the reason why I'd love to have negative values for > the durations. It would open the possibility of doing something like > "accounting" of time. I think you can do accounting of time without introducing negative duration. Basic accounting implies having two categories. You expect them to be "positive" and "negative", but it could also be "positive in property A" and "positive in property B". > I'm working with self defined duration units and it would be of great > value to be able to calculate the balance for planned and done work > time. I don't use clocking. > > What'd be wrong about having -0:30 h, -30 min, -2.5 h, -3 d or -3 m? > It'd be an addition no change so there would hoefully be no > incompatibilities. > > Maybe even 3m -3d be or -3m 3d could be of use. No incompatibility doesn't mean no cost. It adds code complexity. You also have to maintain the feature later on, make sure it doesn't break future code, etc. Moreover, I'm not convinced about the general need for such a feature. Of course, it is possible that I may be missing the point. Org folks may want to chime in and correct me if I do. > As I see there is org-duration.el - Have the changes to be made only > there? I think so. But I suggest to check if you cannot do otherwise (again, I'm sure you can).
Re: Bug: org-agenda-tag-filter-preset not respected [9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/jorge/.config/emacs/elpa/27.0/develop/org-plus-contrib-20200302/)]
Hello, Jorge P. de Morais Neto writes: > Hi. I am sorry for insisting, but this bug report is a month old and > has not been added to <https://orgmode.org/worg/org-issues.html>. AFAIK, this file is not maintained anymore. Note that it strength was not the HTML report, but the fact that you could import the Org counterpart in your agenda files. > I have just tested and reproduced it with Emacs 27 -- emacs-27 branch, > snapshot from [2020-04-04 sáb] -- and org-plus-contrib 20200406. > > In this situation, is it OK to remind you of the bug every month? Certainly. Unfortunately, no one volunteered to fix the issue so far. You may want to have a look at it, you will certainly get help doing so. Otherwise, you are welcome to bump the report from time to time. Regards, -- Nicolas Goaziou
Re: Bug: org-archive-subtree-save-file-p logic [9.3.6 (release_9.3.6-399-ge6df03 @ /home/n/.emacs.d/straight/build/org/)]
Kyle Meyer writes: Based on the history above, I believe the main purpose is to give users a way to reverse the "no saving" behavior made in 63f6e851b (Do not save target buffer after archiving subtree, 2017-11-25). I'm _guessing_ that, on top of that, the idea adding a from-agenda value was that some users may want to save only when archiving from the agenda, because in that case they're a bit removed from the buffer and might not think to save it, or something along those lines. Assuming what I said above is true, I think what you propose here loses the ability to save only when archiving from the agenda. And more importantly, users would not be able to give a blanket "don't save" in order to retain the behavior introduced by 63f6e851b (Do not save target buffer after archiving subtree, 2017-11-25). Thanks for the explanation, Kyle. I understand the intent of the variable better now. What do you think of something like this? #+begin_src emacs-lisp (defcustom org-archive-subtree-save-file-p 'unless-agenda "Conditionally save the archive file after archiving a subtree. The value 'unless-agenda prevents saving from the agenda-view. The value 'only-agenda saves only when the archive is initiated from the agenda-view. The value t saves in all cases where the archive target buffer is not the current buffer. The value nil prevents saving in all cases." :group 'org-archive :package-version '(Org . "9.4") :type '(choice (const :tag "Do not save archive buffer when archiving from an agenda view" unless-agenda) (const :tag "Only save archive buffer when archiving from an agenda view" only-agenda) (const :tag "Save the archive buffer unless it is the current buffer" t) (const :tag "Do not save the archive buffer"))) #+end_src #+begin_src emacs-lisp ;;don't save when target buffer is current buffer (unless (eq buffer this-buffer) ;;t always saves (when (or (eq org-archive-subtree-save-file-p t) ;;'unless-agenda saves unless archive initiated from agenda (and (eq org-archive-subtree-save-file-p 'unless-agenda) (not (boundp 'org-archive-from-agenda))) ;;'only-agenda saves iff archive initiated from agenda (and (eq org-archive-subtree-save-file-p 'only-agenda) (boundp 'org-archive-from-agenda))) (save-buffer))) #+end_src This should result in the following scenarios: | org-archive-subtree-save-file-p | called-from-agenda? | buffer saved? | |-+-+---| | t | nil | t | | t | t | t | | only-agenda | nil | nil | | only-agenda | t | t | | unless-agenda | nil | t | | unless-agenda | t | nil | | nil | nil | nil | | nil | t | nil |
Positive experience with org-element API
Hi everyone, I just wanted to share a recent positive experience I had with org-mode, specifically with org-mode parsing in elisp. I maintain a package that allows users to write curl request in org mode and execute them. At first, I defined a structure for that org entry that I was parsing via a series of regex into an alist. But as features grew and the structure evolved, it was becoming incredibly difficult and hacky to parse that way. Thankfully, after spending a bit of time with the org-element API doc and getting some much needed help on the IRC channel, I was able to replace the hacky regex with a cleaner and more robust mechanism taking full advantage of `org-element-map`. In case you are interested in the code, you can see a sample org entry here: https://github.com/abrochard/walkman/blob/master/sample.org and the parsing code here: https://github.com/abrochard/walkman/blob/master/walkman.el#L148 It definitely could me optimized but I am quite happy with it already. Thanks again to everyone for the help and the doc! Best, Adrien Brochard
Re: Org-babel-lilypond always renders full pages
stardiviner writes: > > Can report this bug to ob-lilypond.el maintainer. I have not found any contact > info like email in source code file. Does anyone can get in touch with the > maintainer? > Isn't ob-lilypond.el part of Org mode proper (i.e. not contrib)? If so, this is the place to report bugs for it. The maintainer is the usual suspects :-) (but I'm sure they would appreciate any help anybody can offer). -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: Bug: org-archive-subtree-save-file-p logic [9.3.6 (release_9.3.6-399-ge6df03 @ /home/n/.emacs.d/straight/build/org/)]
No Wayman writes: > What do you think of something like this? Thanks for the suggestion. The code is somewhat oddly formatted, at least on my end. Could you send a proper git-format-patch output to this thread (either via git-send-email or as an attachment)? > #+begin_src emacs-lisp > (defcustom org-archive-subtree-save-file-p 'unless-agenda > "Conditionally save the archive file after archiving a subtree. > The value 'unless-agenda prevents saving from the agenda-view. "an agenda view" sounds better to me and matches the original text from 3d0282ef8. > The value 'only-agenda saves only when the archive is initiated > from the agenda-view. nitpick: Please write symbols as `foo' rather than 'foo. Also, if you're going to expand the docstring (not a bad thing), I think it'd make sense to slim down the :tag text a bit. org-archive-save-context-info provides a nice example of formatting the docstring, including the list of values. > The value t saves in all cases where the archive target buffer is > not the current buffer. > The value nil prevents saving in all cases." > :group 'org-archive > :package-version '(Org . "9.4") > :type '(choice > (const :tag "Do not save archive buffer when archiving > from an agenda view" unless-agenda) > (const :tag "Only save archive buffer when archiving > from an agenda view" only-agenda) As I mentioned above, I have a slight preference for sticking with 3d0282ef8's names: from-org and from-agenda. I suppose the main argument against from-org is that it's not clear from the name alone that it's referring to a non-agenda Org buffer because "org" is of course a bit overloaded. Considered alongside from-agenda, I don't think it's too bad though. > (const :tag "Save the archive buffer unless it is the > current buffer" t) This current buffer bit also applies to unless-agenda/from-org. Perhaps it'd make sense to just mention the current buffer behavior in the main docstring, given it applies to all options (even though for only-agenda/from-agenda, it's never the case that the archive buffer is the current buffer). In summary * I'd prefer to make a more minimal change on top of 3d0282ef8, keeping the names chosen there. Functionally that comes down to adjusting the condition that guards the save-buffer call to consider from-org. * I think it'd be good to expand the docstring (along the lines of what you suggested) as well as trim and clarify the tag text a bit. Thoughts?
Re: R session and plotting in x11 window
On Sun, Apr 5, 2020 at 1:19 PM Berry, Charles wrote: > > > > On Apr 4, 2020, at 4:27 PM, Matt Price wrote: > > > > Does anyone know much about the difference between an R session opened > by typing M-x R, and the R session opened by org-babel? > > > Short answer: almost none. > > Long answer: what `org-babel-R-initite-session' and friends do. > :-) thanks, I should have been looking for that > > > > > I'm just learning R and my usual method for learning a language is to > keep a kind of notebook in org with code snippets they I can execute and > iterate on rapidly as I learn. This works great in R when I'm just doing > math. When I am working on plots, it would be nice to have them open up > quickly either in emacs or in the standard x11 window that R session opened > switch M-x R opens up. > > > > I know I can set the src block headers to produ e a file, but when I'm > just iterating rapidly I often switch back and forth between a data output > and a graphical output, and typing/erasing those headers is clunky and > slow. It would be easier to just paste the plot command into the console > and have it pop open the window... But that doesn't seem to work. Anyone > know if I can tweak something to make that possible? > > > > > I sam really puzzled by this. Do you have an ECM that illustrates this? > > Working interactively on my Mac (Quartz - X11 is the device), I routinely > do what you describe - usually working from the src edit buffer - and the > plots are displayed (and older plots are available via clover-left or some > such). > > If I had to guess, I'd say that you are opening an R session, but not > using it. If you execute a src block, but it does not have a `:session' > header, a new instance of R will create a plot file and then exit. If you > look in the default directory, you would see `Rplots.pdf' or some such. > > The only other thing that comes to mind is that you opened a device that > is holding on to all your plots. Try `dev.cur()' in R immediately before > and after you create a plot and see what the result is. > > This was the problem. I don't see that I'm calling dev.set() anywhere but when the session initiates dev.cur() returns null 1 calling dev.set(1) or dev.set(2) launches an R_x11 window and future plots are displayed there. As I say, I'm just learning R, and I don't really understand how the device is set up. I also don't understand why it would be set to X11 in a plain-old R session, but not in an org-babel R session. Most references to "device" in ~ob-R.el~ seem to be managing file outputs, and "X11". For now I don't think I'll explore a proper solution as I'm already pretty far down a rabit hole just learning R at all! But thanks very much for this workaround. Matt > HTH, > > Chuck > > >
Re: Bug: org-agenda-tag-filter-preset not respected [9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/jorge/.config/emacs/elpa/27.0/develop/org-plus-contrib-20200302/)]
Nicolas Goaziou writes: > Unfortunately, no one volunteered to fix the issue so far. You may want > to have a look at it, you will certainly get help doing so. Otherwise, > you are welcome to bump the report from time to time. This bisects to 7e52b7661 (org-agenda: Fix logic of `org-agenda-filter-make-matcher', 2020-02-19). Jorge, I tested the patch below against the test case you provided, though of course confirmation that it resolves the issue on your end would be appreciated. I'll apply it tomorrow unless there are objections. -- >8 -- Subject: [PATCH] agenda: Fix regression in handling of non-caterory filters * lisp/org-agenda.el (org-agenda-filter-make-matcher): Combine filter forms with `and' unless multiple positive categories are given. 06cf532f4 (org-agenda.el: Fix bug when using category filters, 2020-01-20) modified org-agenda-filter-make-matcher to group the form with `or' rather than `and' for category filters. This logic was tweaked again in a follow-up commit, 7e52b7661 (org-agenda: Fix logic of `org-agenda-filter-make-matcher', 2020-02-19), which was supposed to restrict the use of `or' to _multiple_ positive categories. However, the follow-up commit incorrectly affected all filter types. Avoid the check for non-category types. Also, fix the regexp so that it matches whenever there are multiple positive categories, not just a single one. --- * I'm tempted to drop the multi-pos-cats binding and move the expression in line. I may do that before applying. * I'm not really sure what the behavior should be when there are multiple "+"s and at least one "-". I doubt that there's much sensible to do here, or that it matters one way or the other. lisp/org-agenda.el | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index d89a3da7c..ffb892b0c 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -7948,8 +7948,10 @@ (defun org-agenda-filter-make-matcher (filter type &optional expand) argument EXPAND can be used for the TYPE tag and will expand the tags in the FILTER if any of the tags in FILTER are grouptags." (let ((multi-pos-cats -(string-match-p "\++" - (mapconcat (lambda (cat) (substring cat 0 1)) filter ""))) +(and (eq type 'category) + (string-match-p "\\+.*\\+" + (mapconcat (lambda (cat) (substring cat 0 1)) +filter "" f f1) (cond ;; Tag filter -- 2.26.0
Re: Bug: org-shiftright etc. do not respect org-support-shift-select [9.3.6 (9.3.6-elpa @ /home/vladimir/.emacs.d/elpa/org-9.3.6/)]
Vladimir Panteleev writes: > I have org-support-shift-select set to 'always. As such, when editing > tables, I expect that Shift + arrow keys to enable Emacs shift > selection. Instead, it moves table cells around. > > This behavior did not exist in Org 9.1.9. The change in behavior happened with 09f950723 (Added keybindings for `org-table-move-cell-*' functions), which was a part of the v9.3 release. Looking at that commit and scanning the associated thread [^], I'm guessing the interaction with org-support-shift-select was simply overlooked and those org-table-move-cell-* calls should be updated to inspect org-support-shift-select, like (some of) the other neighboring branches in the code. I'll take a look at doing that tomorrow. > The documentation of org-support-shift-select should also be updated > to include tables in the list of contexts where shifted cursor keys > execute Org commands. True. Thanks for the report. [^]: https://yhetil.org/orgmode/cakj7shgdxaor6lwe+pg481z7dyhxxr6ddwrbwga2vcyx+rk...@mail.gmail.com/T/#u
