Re: Feature request: kill-buffer for org-capture-finalize

On Fri, Sep 08, 2023 at 12:38:07PM +, Ihor Radchenko wrote: > Did you consider :kill-buffer property in `org-capture-templates'? > > :kill-bufferIf the target file was not yet visited by a buffer when > capture was invoked, kill the buffer again after capture >

Re: Feature request: kill-buffer for org-capture-finalize

On Fri, Sep 08, 2023 at 12:10:23PM +, Ihor Radchenko wrote: > Eduardo Suarez writes: > > > The function org-capture-finalize allows an argument to 'jump-to-capture'. I > > think it may be a good idea to add a new argument to 'kill-buffer' after the > > capture is finalized. This would be usef

Re: Attachment example with inlineimages

My fault. The reason seems to be a doom emacs advice. https://github.com/doomemacs/doomemacs/issues/7222 https://github.com/doomemacs/doomemacs/blob/07fca786154551f90f36535bfb21f8ca4abd5027/modules/lang/org/config.el#L866 On Thu, Jun 22, 2023 at 10:12:50AM +, Ihor Radchenko wrote: > Eduardo S

Re: [off-topic] E-readers and Org-Mode

FTR, I'm a happy Onyx Boox user. I considered remarkable, but I read somewhere (can't find it) that handwritten PDF annotations were not coded as vector graphics, so I went for Onyx.

Re: Planning links to tasks

Org sample fixed: BEGIN ORG SAMPLE ... * Planning ** Planned tasks - [[#task4][My task 4 header]] - [[#task5][My task 5 header]] - [[#task1][My task 1 header]] - [[#task2][My task 2 header]] - [[#task7][My task 7 header]] - [[#task6][My task 6 header]] - [[#task3][My task 3 header]] *

Re: Manual Ordering and Dynamic Priority

> previously spent actually getting the job done. > > The other danger is of course that we become too dependent on the > technology. We can see this happening now with information like phone > numbers. Even only 20 years ago, most people would memorise and be able > to recall many

Re: Local visibility makes header always visible

Would you consider this as a bug? On Sat, Apr 09, 2022 at 09:27:36PM +0100, Eduardo Suarez wrote: > Say next org file, where I want the content of entry ABA not to be shown (e.g. > because it is not important). > > --- BEGIN ORG FILE --- > #+STARTUP: content > * A > ** AA > ** AB > *** ABA > :PRO

Re: [PATCH] Re: Escaping org mode date properties

On Mon, Jan 03, 2022 at 11:39:19AM +0800, Ihor Radchenko wrote: > Eduardo Suarez-Santana writes: > > > However, how about next cases? > > > > * an example block > > #+begin_example > > SCHEDULED: <2015-02-16 Mon .+2d> > > #+end_example > > I

Re: [PATCH] Re: Escaping org mode date properties

On Sun, Jan 02, 2022 at 10:51:54AM +0800, Ihor Radchenko wrote: > Eduardo Suarez-Santana writes: > > >> I am unable to reproduce. What are your Org and Emacs versions? > > > > I'm using Spacemacs (develop branch). > > > > - Emacs 27.2 > > -

Re: Escaping org mode date properties

On Sat, Jan 01, 2022 at 11:10:30PM +0800, Ihor Radchenko wrote: > Eduardo Suarez writes: > > > The next code snippet makes the entry to appear in the agenda: > > > > * sample date code > > #+begin_src org > > SCHEDULED: <2015-02-16 Mon .+2d> > > #+end_src > > I am unable to reproduce. What are y