[O] Bug: ‘(org-resolve-clocks)’ picks the wrong target for placing a new clock-drawer when ‘org-clock-out-remove-zero-time-clocks’ is set to t [9.1.14 (9.1.14-9-g131531-elpa @ ~/.emacs.d/elpa/org-2018

drawer-name)) (case-fold-search t)) (when drawer (let ((re (format "^[ \t]*:%s:[ \t]*$" (regexp-quote drawer))) (end (save-excursion (org-end-of-subtree (while (re-search-forward re end t) (org-remove-em

Re: [O] Bug: ‘(org-resolve-clocks)’ picks the wrong target for placing a new clock-drawer when ‘org-clock-out-remove-zero-time-clocks’ is set to t [9.1.14 (9.1.14-9-g131531-elpa @ ~/.emacs.d/elpa/or

Hello, Thank you for your quick patch. Since I wasn’t able to solve it on my own, I’ll take a look at your solution to understand what you did. Have a great day. Best, Nicolas Goaziou writes: Hello, Leo Vivier writes: Hello, There seems to be a bad interaction between ‘(org-resolve

[O] [PATCH] org.el: Fix newline at eob in org-insert-heading

* lisp/org.el (org-insert-heading): Check if narrowed before inserting newline at eob When narrowed into an org-buffer (e.g. when capturing), adding a new heading with C- or M- on the last line of a buffer (i.e. that not without a newline at the end) would result in the insertion of a newline at t

[O] [PATCH] org.el: Fix newline at eob in org-insert-heading

* lisp/org.el (org-insert-heading): Check if narrowed before inserting newline at eob When narrowed into an org-buffer (e.g. when capturing), adding a new heading with C- or M- on the last line of a buffer (i.e. that not without a newline at the end) would result in the insertion of a newline at t

[O] Bug: Bug: org-clock commands spawn drawer outside of narrowing [9.2.1 (9.2.1-2-gc6d37c-elpaplus @ /home/zaeph/.emacs.d/elpa/org-plus-contrib-20190204/)]

finicky than I anticipated, and I’d hate to break anything. Would you be able to look into it? Thank you for your time, -- Leo Vivier English Studies & General Linguistics Master Student, English Department Université Rennes 2

Re: [O] Bug: Bug: org-clock commands spawn drawer outside of narrowing [9.2.1 (9.2.1-2-gc6d37c-elpaplus @ /home/zaeph/.emacs.d/elpa/org-plus-contrib-20190204/)]

Hello, I’d forgotten to CC the list in my previous message, so I’ve included all the context from our two previous emails. Nicolas Goaziou writes: > Leo Vivier writes: > >> You’re right, that’s the behaviour we would expect from M-RET. However, >> with C-RET, the new head

Re: [O] [PATCH] org.el: Fix newline at eob in org-insert-heading

you know if I encounter anything unexpected. Best, P.S.: I’d sent the patches with the wrong email. This is now resolved. -- Leo Vivier English Studies & General Linguistics Master Student, English Department Université Rennes 2

[O] [PATCH 2/2] Prevent deletion of newline added by narrowing

* lisp/org.el (org-delete-backward-char): Prevent deletion of newline added by narrowing (org-delete-char): Prevent deletion of newline added by narrowing (org-kill-line): Prevent deletion of newline added by narrowing (org-kill-region): Create wrapper for `kill-region' to prevent deletio

[O] [PATCH 1/2] Fix narrowing for 1-line subtrees

* lisp/org.el (org-narrow-to-subtree): Ensure newline at end of subtree. (org-tree-to-indirect-buffer): Ensure newline at end of subtree. (org-widen): Create wrapper for `widen' to handle end newline. * lisp/org-capture.el (org-capture-finalize): Replace `widen' with `org-widen'. (org-

[O] [PATCH] Fix other commands for exiting narrowing

* lisp/org.el (org-kill-buffer): Create a wrapper for kill-buffer to handle last newline deletion. (org-kill-buffer-and-window): Create a wrapper for kill-buffer-and-window to handle last newline deletion. * lisp/org-keys.el (org-remap): Remap kill-buffer and kill-buffer-and-window to or

[O] [PATCH] Fix other commands for exiting narrowing (2)

* lisp/org.el (org-toggle-narrow-to-subtree): Different interactive calls and use wrapper for widen --- Same deal as the last email. Sorry for only noticing those commands now; I don't use them in my workflow. The change in `interactive' is to ensure that only the interactive calls to `org-na

[O] [PATCH] Fix problems

* lisp/org-capture.el (org-capture-narrow): Fix point position after narrowing. * lisp/org-keys.el (org-remap): Remove remaps for `kill-buffer' and `kill-buffer-and-window'. * lisp/org.el (org-tree-check-narrowing): Use `kill-buffer-hook' instead of wrappers for kill-region commands. (o

Re: [O] [PATCH 1/2] Fix narrowing for 1-line subtrees

and gauge whether it affects your workflow negatively? I know you’ve only said that this patch was heading in a wrong direction rather than saying that all hell would break loose upon applying the patch, but the later commits have tried to iron out the kinks, and that might quell your wariness

[O] [PATCH] Fix narrowing for 1-line subtrees (squashed)

This is a squashed version of all the commits I’ve done on that branch to make it easier to apply. --- lisp/org-capture.el | 12 ++-- lisp/org-keys.el| 2 ++ lisp/org.el | 69 - 3 files changed, 67 insertions(+), 16 deletions(-) diff

Re: [O] [PATCH 1/2] Fix narrowing for 1-line subtrees

wed (or at the end of a buffer), if you press : - `point' moves to '2'. - Table is realigned. - Newline is added at the end of the table. [2] We've already addressed `org-clock-out-when-done', but I've found another one. Although adding scheduling/deadline information w

Re: [O] [PATCH 1/2] Fix narrowing for 1-line subtrees

Hello again, Leo Vivier writes: > I was pleased to see that property-adding functions didn't behave badly > with 1-line subtrees. Maybe we could investigate those commands and > patch their behaviour onto the problematic ones? > > If that sounds good to you, I could w

Re: [O] [PATCH 1/2] Fix narrowing for 1-line subtrees

+ (otherwise (error "Invalid planning type: %s" what))) " ") ;; Insert associated timestamp. (let ((ts (org-insert-time-stamp -- 2.20.1 -----[END]- Best, -- Leo Vivier English Studies & General Linguistics Master Student, English Department Université Rennes 2

Re: [O] [PATCH 1/2] Fix narrowing for 1-line subtrees

the condition tree for `org-add-planing-info'. I’ll update you when I’ve made progress. Thanks. Best, -- Leo Vivier English Studies & General Linguistics Master Student, English Department Université Rennes 2

[O] [PATCH] Fix narrowed 1-line subtrees

* lisp/org.el (org-add-planning-info): Ensure insertion in current restriction. (org-remove-timestamp-with-keyword): Respect ambiguous newline when narrowed to 1-line-subtree. (org-remove-empty-drawer-at): Respect ambiguous newline when narrowed to 1-line subtree. (org-entry-delete): Re

Re: [O] [PATCH] Fix narrowed 1-line subtrees

[START] * Tree 1{ :PROPERTIES: :TEST: t :END:} * Tree 2 -[END]- It's likely that I haven't addressed all the commands that do not play well with the ambiguous newlines

[O] [PATCH] Fix spaces with `org-remove-timestamp-with-keyword'

* lisp/org.el (org-remove-timestamp-with-keyword): Fix space deletion between timestamps When an entry had a CLOSED, a DEADLINE and a SCHEDULED timestamps, removing the middle one caused the space between the 1st and 3rd to be removed as well. Checking whether we’re at the end of the line befor

Re: [O] [PATCH] Fix narrowed 1-line subtrees

-less clocking. You'll find those three patches at the bottom alongside another with all the patches until now squashed together (except the patch for `org-remove-timestamp-with-keyword' which wasn't related). HTH. Best, -- Leo Vivier English Studies & General Linguistics

Re: [O] [PATCH] Fix narrowed 1-line subtrees

Hello again, Leo Vivier writes: > You'll find those three patches at the bottom alongside another with all > the patches until now squashed together (except the patch for > `org-remove-timestamp-with-keyword' which wasn't related). I ended up sending the wrong patc

Re: [O] [PATCH] Fix narrowed 1-line subtrees

ir share of complexity. >From my point of view, I do not see it as 'complex', but rather as a different way from doing what we'd been doing so far. Most of the functions are only *slightly* modified to preserve the ambiguous newline. HTH. Best, -- Leo Vivier English Studies &a

Re: [O] [PATCH] Fix narrowed 1-line subtrees

get a chance to corrupt anything. 2. We address *past corruptions* by adding a function to `org-lint' which catches corrupted subtrees and throw a warning. HTH. Best, -- Leo Vivier English Studies & General Linguistics Master Student, English Department Université Rennes 2

[O] Bug: org-tables: Broken alignment when using numbers of different lengths [9.1.5 (9.1.5-1-gb3ddb0-elpa @ .emacs.d/elpa/org-20171225/)]

quot;ftp" :follow (lambda (path) (browse-url (concat "ftp:" path))) ) ("help" :follow org--open-help-link) ("http" :follow (lambda (path) (browse-url (concat "http:" path))) ) ("https" :follow (lambda (path) (browse-url (concat "https:" path))) ) ("mailto" :follow (lambda (path) (browse-url (concat "mailto:"; path))) ) ("news" :follow (lambda (path) (browse-url (concat "news:"; path))) ) ("shell" :follow org--open-shell-link)) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) ) -- Leo Vivier English Studies & General Linguistics Language Scholar, French Department Reed College

[O] Bug: org-tables: Broken alignment when using numbers of different lengths [9.1.5 (9.1.5-1-gb3ddb0-elpa @ .emacs.d/elpa/org-20171225/)]

path))) ) ("help" :follow org--open-help-link) ("http" :follow (lambda (path) (browse-url (concat "http:" path))) ) ("https" :follow (lambda (path) (browse-url (concat "https:" path))) ) ("mailto" :follow (lambda (path) (browse-url (concat "mailto:"; path))) ) ("news" :follow (lambda (path) (browse-url (concat "news:"; path))) ) ("shell" :follow org--open-shell-link)) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) ) -- Leo Vivier English Studies & General Linguistics Language Scholar, French Department Reed College

[O] Bug: Modifying org-latex-pdf-process doesn't modify the async export behaviour

g-latex-pdf-process. I'd surmise that async export has a process running in the background, but I don't know how to force it to reload. Would you have any idea? Thanks. Best, -- Leo Vivier English Studies & General Linguistics Master Student, English Department Rennes 2

Re: [O] Bug: Modifying org-latex-pdf-process doesn't modify the async export behaviour

for your prompt reply. Best, On 07/04/18 09:59, Nicolas Goaziou wrote: Hello, Leo Vivier writes: I've encountered an issue trying to write a function to toggle between two org-latex-pdf-process states (short & long). The function works as intended when using synchronous export (the

[PATCH] lisp/org-persist.el (org-persist-gc): Fix pcase pattern

Hi there, Quick patch to fix a typo in a pcase pattern which quotes a function. It results in `(function numberp foo)' when expanded, which in turns throws `(wrong-number-of-arguments function 2)' when eval’d. Best, -- Leo Vivier Freelance Software Developer Website: www.leovivier.

[PATCH] Fix small mistake in doc

Hello, I’ve noticed a small mistake in the doc for `org-time-stamp-inactive`. You’ll find the details in the patch. HTH. Best, -- Leo Vivier >From 021dd8d98b7d8e86fcfdff659cb225be6dc51939 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Wed, 8 Apr 2020 10:22:20 +0200 Subject: [PATCH]

[PATCH] Fix typo in doc

Hello, I’ve spotted a small mistake in the doc. Best, -- Leo Vivier >From b2b2582b4eb1deb1a41f200a17876dfbcbf26b5e Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Sun, 19 Apr 2020 12:01:30 +0200 Subject: [PATCH] * lisp/org.el (org-mode-map): fix typo --- lisp/org-keys.el | 2 +- 1 f

[PATCH] org-element.el: Fix properties being upcased by parser

with some hard-coded upper case letters in the codebase, but I haven’t run into any issue so far. HTH, -- Leo Vivier >From 574549a1ab07fd1500111a25d3f1caec4aa40bfb Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Mon, 8 Jun 2020 12:14:55 +0200 Subject: [PATCH] org-element.el: Fix properties be

Re: [PATCH] org-element.el: Fix properties being upcased by parser

-- Ultimately, it’s not changing anything for the users, but I did find it a little counterintuitive. HTH, -- Leo Vivier

Re: [PATCH] org-element.el: Fix properties being upcased by parser

f it? Best, -- Leo Vivier

[PATCH] org-element.el: Update comment

Hi there, I’ve noticed that a comment on the caching of org-element wasn’t up to date, so I went ahead and updated it. I’ve also fixed a missing quote for one of the variables. HTH, -- Leo Vivier >From bf1fcc1c0650c30e1e12244df084ab344a2cac59 Mon Sep 17 00:00:00 2001 From: Leo Vivier D

Re: [PATCH] org-element.el: Fix properties being upcased by parser

Hello, Nicolas Goaziou writes: > Leo Vivier writes: > >> Yeah, I’ve reached the same conclusion, and I agree that we could >> mention the normalisation in a docstring. Do you want me to take care >> of it? > > Sure! Thank you. The patch is attache

[PATCH] org: Update example in docstring to accommodate new name and new format

Hi there, I’ve spotted an example in a docstring that wasn’t updated when the command was renamed and moved to another file in d34786f2279d0fd02e7d0484e36bc22adc760de2. I took the liberty to update it. HTH, -- Leo Vivier >From 83dde9d0735cc6223233aa18c938a4ae14b4c88c Mon Sep 17 00:00:00 2

Re: [PATCH] org: Update example in docstring to accommodate new name and new format

Hi again, I forgot a closing paren in the previous commit. You’ll find an amended version below, as well as a little more context-lines. Sorry! HTH, -- Leo Vivier >From 01acc00866f14a6e70e3abcb024534c392dc8a27 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Mon, 20 Jul 2020 22:11:15 +0

Re: [PATCH] org: Update example in docstring to accommodate new name and new format

keep the mention. The example itself can go. Thanks for the review. HTH, -- Leo Vivier >From 48b50f0ebb5d21ca6b337d78a16a203888161d43 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Mon, 20 Jul 2020 22:11:15 +0200 Subject: [PATCH] org: Remove useless example in docstring * lisp/org.el (or

Re: [PATCH] org: Update example in docstring to accommodate new name and new format

contribute.html>. You're bumping up > against the tiny change threshold, so please consider submitting the > copyright assignment paperwork. I have already filled the paperwork, and I will send you the scan in a separate email. Could you move me to the list of current contributors? Thanks. Best, -- Leo Vivier

[PATCH] org-capture: Update plist before finalizing

-capture-plist' early in `org-capture-finalize'. I don’t think this would have unforeseen effects, since `org-capture-list' is already meant to be transient, and we’d only be expanding its use from init-only to init-and-exit. HTH, -- Leo Vivier >From d14f15ab76d60c3f65837a6d1471

Re: [PATCH] org-capture: Update plist before finalizing

ith the docstring for `org-capture-current-plist'. You’ll find the amended commit below. Best, -- Leo Vivier Freelance Software Engineer Website: www.leovivier.com | Blog: www.zaeph.net >From ab47e50dae4029622d3e8378f816f77153c180d9 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Sat,

Re: a catastrophic orgmode issue - a definite show stopper, put on your tin hats

c hold-up on the next release. Best, -- Leo Vivier Freelance Software Engineer Website: www.leovivier.com | Blog: www.zaeph.net

Re: Shower thought: submit an IETF RFC to register Org as a MIME type

th a vested interest in developing an efficient external parser for Org documents, I’d love to contribute. I’ve been playing around lately with ox.el to write an exporter to Jupyter (more on that soon), and since it makes extensive use of org-element.el, I’d have a modicum of knowledge upon which I co

Re: Shower thought: submit an IETF RFC to register Org as a MIME type

would that be > confusing? Since we already have worg/dev/org-element-api.org [1], I think the rename to worg/dev/org-element-syntax.org would be welcome. Notes : [1] https://orgmode.org/worg/dev/org-element-api.html -- Leo Vivier Freelance Software Engineer Website: www.leovivier.com | Blog: www.zaeph.net

Re: New website - back to the old unicorn!

on that page is that we’re grabbing the picture from remote domains, which means that users of uMatrix have to greenlight them before they can be displayed. A solution could be to host them ourselves, which should have a minimal footprint. Best, -- Leo Vivier Freelance Software Engineer Webs

Re: Interest in an Org video meetup?

at talk you’d like to extract and share. Let me know what you're interested in and we’ll set you up with everything. :) Notes: [0] BigBlueButton (BBB) is FLOSS Video conferencing suite. For details, see: https://bigbluebutton.org/ [1] https://openai.com/blog/whisper/ Best, -- Leo Vivier