Re: org-ctags land grab

Ihor Radchenko writes: > Nick Dokos writes: > >> `org-ctags' unilaterally sets the hook `org-open-link-functions' to a >> bunch of org-ctags functions and enables itself by default. That has >> the unfortunate consequence of invalidating the documentation for >> internal CUSTOM_ID links - see >>

[PATCH] Make predicates non-interactive

Predicates like `org-first-sibling-p' are no use when called interactively, and should not appear in the M-x prompt. TINYCHANGE --- lisp/org.el | 3 --- 1 file changed, 3 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 23cb6012d..20e6ea6d9 100644 --- a/lisp/org.el +++ b/lisp/org.el @@

Re: [SUGGESTION] ob-shell async result output should not contains shell prompt

On Wed, 22 Mar 2023 23:25:50 -0400 Christopher M. Miles wrote --- > > The ob-shell async result output contains the shell prompt. I think it > should not be captured. > > #+begin_src shell :session "test2" :async t > sleep 30 > echo "hello, world" > #+end_src > > #+RESULTS[(

[CANCELED] Re: [BUG] org-capture got file userlock error when I capture on second time.

Ihor Radchenko writes: > stardiviner writes: > >> When I org-capture from elfeed-entry buffer (I defined custom functions to >> extract elfeed entry buffer content) in the second time and later, the >> bellowing error raised up. The first-time capture is fine. >> >> Here is the error backtrace:

[SUGGESTION] ob-shell async result output should not contains shell prompt

The ob-shell async result output contains the shell prompt. I think it should not be captured. #+begin_src shell :session "test2" :async t sleep 30 echo "hello, world" #+end_src #+RESULTS[(2023-03-23 11:19:22) 461ed5de684f6e619890709175ec73e80b67b2d6]: : bash-5.2$ hello, world -- [ stardivine

Re: [BUG] Agenda not sorting by priority THEN todo state (todo state ignored) [9.6.1 (9.6.1-??-fe92a3c @ /Users/polofsson/.emacs.d/.local/straight/build-28.2/org/)]

perhaps we could have 2 names: one for the priority cookie setting and one for whatever the agenda does. On 3/22/23, Ihor Radchenko wrote: > Jonas Olofsson writes: > >> I am trying to sort my agenda by a number of variables, but it seems >> that todo-state-down is not applied if added after pri

Re: [PATCH] org-user-idle-seconds: Add support for logind

Ihor Radchenko writes: > Nathaniel Nicandro writes: > >> I would like to submit a patch that adds support for logind to >> `org-user-idle-seconds`. This patch has been working for me for a long >> while now and I thought it time for me to submit it. I've contributed >> to Emacs in the past so

Re: Two low-priority questions re: design of org-babel-do-load-languages

Ihor Radchenko wrote (Wed, Mar 22, 2023 at 12:55:31PM +): > The function `org-babel-do-load-languages' is originally not a generic > function. It is specifically designed to be used as a :set function for > `org-babel-load-languages' variable: > > (defcustom org-babel-load-languages '((emacs-l

Re: [PATCH] org-user-idle-seconds: Add support for logind

Hi, Ihor Radchenko writes: > Though I do not see any commits associated with Nathaniel Nicandro or > your email in Emacs git repo. > Bastien, may you check FSF records? Nathaniel's records are okay. -- Bastien Guerry

Re: [PATCH v2] org-manual.org: $n$-th is not math

Timothy writes: > I feel the need to point out that this way lies madness. > > The behaviour [...] “weird things are happening”. Thank you so much for taking the time to explain the problem to me; I now understand it much better! That said, if the heuristic is $ ...MATH... $- then `$3 o

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

Daniel Ortmann writes: > Ihor, > > * In an org buffer, input: [1960-10-16] > * Set point between the brackets. > * Press C-c ! and enter. > * The result is [19_*7*_0-10-16 Fri] > * I expected [1060-10-16-Sun] > > Yes, C-c C-c works. > > But C-c ! enter is supposed to use [1960-10-16] as

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

Ihor, * In an org buffer, input: [1960-10-16] * Set point between the brackets. * Press C-c ! and enter. * The result is [19_*7*_0-10-16 Fri] * I expected [1060-10-16-Sun] Yes, C-c C-c works. But C-c ! enter is supposed to use [1960-10-16] as the default date and not change that date to 1

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

Daniel Ortmann writes: > Since that existing timestamp at point is supposed to be used as the > default, we definitely have a bug > ==>> ... Since that 'default' time is bumped up to 1970. > > Clearly, the expected default behavior is not working as expected. > (Times after 1970 are fine.) May

Re: ox-beamer/latex questions

Ihor Radchenko writes: > Leo Butler writes: > >>> This is because >>> *** DONE :B_block: >>> is actually parsed as a heading with DONE todo keyword and title >>> ":B_block:". Tag is not recognized. >>> >>> We probably need to fix it, though I am not sure. It is one of the edge >>> cases about O

Re: [External] : Re: [BUG] updating existing org date with time always sets time to 0:00 [9.6.1 (release_9.6.1-262-gd94f40 @ /home/dortmann/src/git-org-mode/lisp/)]

Since that existing timestamp at point is supposed to be used as the default, we definitely have a bug ==>> ... Since that 'default' time is bumped up to 1970. Clearly, the expected default behavior is not working as expected. (Times after 1970 are fine.) On 2/22/23 04:57, Ihor Radchenko wrot

Re: [PATCH] Fix one remaining emacs-30 byte-compile warning

Bastien Guerry writes: > Ihor Radchenko writes: > >> Sure, but we need to confirm with FSF records first. >> Bastien, may you take a look? > > Yes, I confirm Arash records are okay, sorry for the delay. Updated WORG page. https://git.sr.ht/~bzg/worg/commit/bf040f8a -- Ihor Radchenko // yantar

Re: [PATCH] Fix one remaining emacs-30 byte-compile warning

Ihor Radchenko writes: > Sure, but we need to confirm with FSF records first. > Bastien, may you take a look? Yes, I confirm Arash records are okay, sorry for the delay. -- Bastien Guerry

Re: [PATCH v2] org-manual.org: $n$-th is not math

Hi Rudolf, > Funny, I the exact opposite of you; I would pay many to see $…$th and > $…$-th special-cased (with tests, so that it would not break again). I feel the need to point out that this way lies madness. The behaviour of $ in Org is /inherrently/ confusing. You’re confused by `$...$th' a

Re: Hyphen after LaTeX fragments

Dominik Schrempf writes: >>> I think this is HIGHLY confusing. I think we should write something >>> along the lines: "Do not use $...$. Only for reasons of backwards >>> compatibility, $...$ syntax is partly (!) supported." >> >> Feel free to provide a patch. > > I think that a change in the doc

Re: Two low-priority questions re: design of org-babel-do-load-languages

Mandar Mitra writes: > Here's the code from my version of org.el (9.5.5, inbuilt in Emacs 28.2). > > (defun org-babel-do-load-languages (sym value) > ... > 1. Question from purely a programming student's perspective: this seems to be > doing two things: (i) a set-default on line 3, and (ii) actu

Re: Hyphen after LaTeX fragments

Ihor Radchenko writes: > Dominik Schrempf writes: > >> Maybe the best thing to do is drop support for $...$ completely? > > We cannot do it. Otherwise, existing Org documents may be broken. > Well, and as detailed later in my mail, I meant deprecating support for $...$. But thanks for pointin

Re: Hyphen after LaTeX fragments

Yuchen Guo writes: > If it is deprecated in Org mode, maybe we can print a warning message in > echo area? Not in echo area, but we can add a linter. >From 129e3aa03229fd2e5dd6ea9bf627e4d95a061744 Mon Sep 17 00:00:00 2001 Message-Id: <129e3aa03229fd2e5dd6ea9bf627e4d95a061744.1679488572.git.yant

Re: Hyphen after LaTeX fragments

Dominik Schrempf writes: > Maybe the best thing to do is drop support for $...$ completely? We cannot do it. Otherwise, existing Org documents may be broken. > I quote the Org mode manual section about $...$ syntax: > > Text within the usual LaTeX math delimiters. To avoid conflicts with >

Re: [PATCH] org-user-idle-seconds: Add support for logind

Nathaniel Nicandro writes: > I would like to submit a patch that adds support for logind to > `org-user-idle-seconds`. This patch has been working for me for a long > while now and I thought it time for me to submit it. I've contributed > to Emacs in the past so my paperwork should be on file.

Re: [bug] org-columns-edit-value will capitalize property

Ok. I will try to send my first patch. Desired behavior is: by using command 'org-columns-edit-value' do not change 'property' name, just its value. On Wed, 22 Mar 2023 at 12:52, Ihor Radchenko wrote: > Sławomir Grochowski writes: > > > After updating the value of property using command > 'org-

Re: [PATCH] Async evaluation in ob-shell

Matt writes: > Unfortunately, I was mistaken and the second option (removing the space from > `org-babel-sh-prompt') doesn't fix the issue. The TLDR is that the code in > `org-babel-comint-async-filter' which grabs the region between the indicators > (incorrectly) fails to include the prompt'

Re: [BUG] incorrect result with C-c ! to correct (complete) a date [9.7-pre (release_9.6.1-306-ga645a6 @ /home/d/src/git-org-mode/lisp/)]

On 22/03/2023 12:34, Daniel Ortmann wrote: Adjusting [1960-10-16] fails with C-c ! Something to do with the epoch boundary? It seems you have not noticed the following message that was sent to the list only without your address in Cc Nick Dokos to emacs-orgmode. Re: [BUG] incorrect result w

Re: Bugfix release request / agenda* fix

Дмитрий Логвиненко writes: > It would be very kind of you if you could make a bugfix release > including this patch. If there are no objections, I will tag a minor bugfix release this weekend. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: org-ctags land grab

Nick Dokos writes: > `org-ctags' unilaterally sets the hook `org-open-link-functions' to a > bunch of org-ctags functions and enables itself by default. That has > the unfortunate consequence of invalidating the documentation for > internal CUSTOM_ID links - see > > https://emacs.stackexchange.co

Re: [bug] org-columns-edit-value will capitalize property

Sławomir Grochowski writes: > After updating the value of property using command 'org-columns-edit-value' > it will capitalize the property name. > > As I understand, "Org is standardized on lower case" > https://list.orgmode.org/87tuuw3n15@nicolasgoaziou.fr/. > > Is this a bug? This is for

Re: [PATCH v2] org-manual.org: $n$-th is not math

On 21/03/2023 23:38, Rudolf Adamkovič wrote: Funny, I the exact opposite of you; I would pay many to see $...$th and $...$-th special-cased (with tests, so that it would not break again). I do not think it is realistic. It may require models for various natural languages and for math expressi

Re: [BUG] incorrect result with C-c ! to correct (complete) a date [9.7-pre (release_9.6.1-306-ga645a6 @ /home/d/src/git-org-mode/lisp/)]

Daniel Ortmann writes: > Starting with this manually-typed birthday date: > [1960-10-16] > Use the arrows to move to the text. > Now press C-c ! and then ENTER As documented in 8.2.1 The date/time prompt section of Org manual: Not all dates can be represented in a given Emacs implementat

[bug] org-columns-edit-value will capitalize property

Hello, After updating the value of property using command 'org-columns-edit-value' it will capitalize the property name. As I understand, "Org is standardized on lower case" https://list.orgmode.org/87tuuw3n15@nicolasgoaziou.fr/. Is this a bug? Btw. interesting article about using upper cas

Re: [BUG] org-capture got file userlock error when I capture on second time.

stardiviner writes: > When I org-capture from elfeed-entry buffer (I defined custom functions to > extract elfeed entry buffer content) in the second time and later, the > bellowing error raised up. The first-time capture is fine. > > Here is the error backtrace: > #+begin_example > Debugger ente

Re: [BUG] org-at-timestamp-p not correctly detecting when at a timestamp [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

Eddie Drury writes: > I've written the following function to test it: > > > (defun my/test-timestamp () > (interactive) > (if (org-at-timestamp-p) > (message "Point is at timestamp") > (message "Point is not at timestamp"))) > > When I run this on a timestamp (either activ

Re: [BUG] Agenda not sorting by priority THEN todo state (todo state ignored) [9.6.1 (9.6.1-??-fe92a3c @ /Users/polofsson/.emacs.d/.local/straight/build-28.2/org/)]

Jonas Olofsson writes: > I am trying to sort my agenda by a number of variables, but it seems > that todo-state-down is not applied if added after priority-down. > Instead it seems as if Priority first is applied, then the date the > item is scheduled. > > Repro: > 1. Set >org-agenda-sorting

[BUG] org-at-timestamp-p not correctly detecting when at a timestamp [9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)]

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. --

Re: [patch] ob-clojure: Fix results output

Daniel Kraus writes: > Ihor Radchenko writes: > >> I note that we now have a new compiler warning after your changes: >> ⛔ Warning (comp): ob-clojure.el:268:45: Warning: Unused lexical argument >> ‘params’ >> >> May you please take a look? >> If the function argument is really unused, replace i

Re: Org Table Header bug?

Ypo writes: > The heading and first lines of the table: > > |---+---+-| > | NPS (~\Oslash_int pulg.) | DN (~\Oslash_int mm) | PP/PE (\Oslash_ext mm) | > |---+---+-| > | 1/8"  | DN 6  | PE 1

Re: [PATCH] lisp/ob-scheme.el

Zelphir Kaltstahl writes: > I've created a patch, which I will attach to this e-mail. Thanks! > Not sure it meets all formalities. For example it is not clear to me, whether > I > should add the "TINYCHANGE" at the bottom of my commit message. You should, unless you have FSF copyright assign

Re: [PATCH] Add tests for ob-haskell (GHCi)

Bruno Barbier writes: > Ihor Radchenko writes: > >> From a first look, random failures appear to be related to session >> initialization. > > My function 'test-ob-haskell-ghci' should protect against that; it > ensures the "*haskell*" buffer is always new. From what I understand, > this is an i

Re: 1 character fix to make ob-haskell compatible with table outputs

ParetoOptimalDev via "General discussions about Org-mode." writes: > Oh, great to hear it's fixed! Sorry, I was not clear. I do not know if the bug existed to start with. I just cannot reproduce on the latest main, which can be for many reasons, starting from me misunderstanding the bug, or mayb