Re: forms and org-mode

2021-08-21 Thread Tim Cross
Ihor Radchenko writes: > Greg Minshall writes: > >> wasn't there also some talk a while back about whatever form'ish >> technology "magit" uses? my sense was it provides something similar to >> Emacs forms. > > To clarify, I am not aware about Emacs forms (unless you refer to > widgets used i

Re: Bug: org-timestamp-{down,up} with numeric argument on time range modifies length [9.4.6 (9.4.6-gab9f2a @ /gnu/store/yg6kjzigqyfzbkzj99xmwmv3nssvhvnq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6

2021-08-21 Thread Tim Cross
Confirm. I am able to confirm this bug using Emacs 27.2 and org 9.4.6 from ELPA. It seems that when changing the first time interval with a C-u argument to set the amount of change, the units are not applied to the second time in the interval, it always changes by 5. So [2021-08-22 Sun 10:00-1

Re: S-M-{,} on CLOCK timestamp

2021-08-21 Thread Tim Cross
"Jorge P. de Morais Neto" writes: > Keywords: org-timestamp-down org-timestamp-up > > Hi. Suppose the buffer has the following text: > > * Task A > :LOGBOOK: > CLOCK: [2021-08-21 sáb 18:00]--[2021-08-21 sáb 18:10] => 0:10 > :END: > > * Task B > :LOGBOOK: > CLOCK: [2021-08-21 sáb 18:18] > :END

Re: Bug: File variable no longer on first line when running org-id-get-create [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]

2021-08-22 Thread Tim Cross
I would argue this is an org-roam bug rather than an org bug and so needs to be reported to the org-roam maintainers. org-roam is not part of org mode. Peter Prevos writes: > Hi, I use file variables on the first line of some Org mode files to indicate > the local Flyspell dictionary, e.g.: >

Re: What happened to ./contrib?

2021-08-25 Thread Tim Cross
The contrib directory has been broken out into its own git repository at https://git.sr.ht/~bzg/org-contrib and the main org repository is moving to be hosted on savannah.gnu.org (I think it is mirrored there already). This is all in preparation for having the contrib extensions available as an

Re: Bug Re: Greater than, less than bug in emacs-lisp source block

2021-09-03 Thread Tim Cross
I think what is happening here is that org is bumping up against fundamental design limitations of Emacs. In basic terms, much of Emacs' underlying design is based on an assumption that a file only has a single major mode. Org works hard to get around this limitation, but it comes with cost - usu

Re: Bug Re: Greater than, less than bug in emacs-lisp source block

2021-09-04 Thread Tim Cross
--- > Professor John Kitchin (he/him/his) > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 > @johnkitchin > http://kitchingroup.cheme.cmu.edu > > On Fri, Sep 3, 2021 at 9:4

Re: Bug Re: Greater than, less than bug in emacs-lisp source block

2021-09-05 Thread Tim Cross
Arthur Miller writes: > I haven't tested the updated version of JK's proposal, but looking at the > source > it seems to be a tad bit resource heavy. If it isn't a hassle for the OP to > use > aliases like lt, gt or similar, I would suggest that either using macros or > simple defalias to ren

Re: [BUG?][PATCH] Should the `lexical-binding' variable be bound during src block with :lexical t? [9.4.6 (9.4.6-ga451f9 @ /home/n/.emacs.d/straight/build/org/)]

2021-09-09 Thread Tim Cross
No Wayman writes: > I ran into this with some code I'm writing which checks against > `lexical-binding'. > Should the following result in "lexical binding enabled" or > "lexical binding disabled"?: > > #+begin_src emacs-lisp :lexical t > (message "lexical binding %sabled" (if lexical-binding

Re: S-M-{,} on CLOCK timestamp

2021-09-13 Thread Tim Cross
Timothy writes: > Hi Tim, > > Jorge P. de Morais Neto writes: > >> I am sorry, my description of the initial condition was incomplete. To >> reproduce the problem, you cannot simply copy the provided text to an >> Org buffer. You should create the clock timestamps with actual clocking >> com

Re: Publish error: wrong argument number

2021-09-16 Thread Tim Cross
Colin Baxter writes: >> Colin Baxter writes: > > > Hello, Today I get a "wrong-number-of-arguments" publish > > error. This was not present a few weeks ago. It is also not > > present in Org-version 9.4.4 but does occur in the latest version > > of org-mode. > > > I'd a

Re: S-M-{,} on CLOCK timestamp

2021-09-24 Thread Tim Cross
Timothy writes: > Hi Tim, > > Jorge P. de Morais Neto writes: > >> I am sorry, my description of the initial condition was incomplete. To >> reproduce the problem, you cannot simply copy the provided text to an >> Org buffer. You should create the clock timestamps with actual clocking >> com

Re: Bug: Org mode fails to compile using Emacs 24.5-r10 [9.4.5 (9.4.5-g3ea248 @ /home/yantar92/.emacs.d/straight/build/org/)]

2021-09-28 Thread Tim Cross
Bastien writes: > Hi Tim, > > Tim Cross writes: > >> I do think it is probably time to drop support for Emacs 24 in the next >> major release. However, we cannot drop it 'mid release'. > > I've added a section called "Compatibility with Emacs

Re: Bug: Org mode fails to compile using Emacs 24.5-r10

2021-09-28 Thread Tim Cross
Max Nikulin writes: > On 28/09/2021 12:33, Bastien wrote: >> Tim Cross writes: >> >>> I do think it is probably time to drop support for Emacs 24 in the next >>> major release. However, we cannot drop it 'mid release'. >> I've added a

Re: Merging latest org-mode for Emacs 28.1

2021-09-28 Thread Tim Cross
Stefan Kangas writes: > Hi org-mode, > > Stefan Kangas writes: > >> As a heads up, Emacs is getting ready to cut the emacs-28 branch in >> preparation of the upcoming release of Emacs 28.1: >> >> https://lists.gnu.org/archive/html/emacs-devel/2021-07/msg00812.html >> >> It would be good if

Re: Merging latest org-mode for Emacs 28.1

2021-09-28 Thread Tim Cross
Timothy writes: > Hi Tim, > >> A new version org 9.5 is going to be released this week. Not sure if >> Emacs maintainers want to bundle this new version or prefer to just >> continue with current 9.4 version. I suspect the latest 9.4 will be the >> preferred version given 9.5 is only going to

<    4   5   6   7   8   9