On Sun, Sep 10, 2023 at 10:57:46AM +, Ihor Radchenko wrote:
> Then, what you can do is
>
> (defun my-org-capture-finalize (arg)
> "Like `org-capture-finalize', but kill Org buffer with double prefix arg."
> (interactive "P")
> (if (equal arg '(16))
> (save-excursion
>
On Sun, Sep 10, 2023 at 08:19:25AM +, Ihor Radchenko wrote:
> (defun my-org-capture-kill-buffer ()
> (when (equal current-prefix-arg '(16))
> (save-excursion
> (org-capture-goto-last-stored)
> (kill-buffer
Thanks for the proposed solution. I have tried it and
On Sat, Sep 09, 2023 at 09:18:27AM +, Ihor Radchenko wrote:
> For personal use-case, you can utilize
> `org-capture-after-finalize-hook', checking `current-prefix-arg' and
> killing the target org buffer according to the prefix argument passed.
> Then, for example, you can make C-u C-u C-c C-c
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
>
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
This is a feature request.
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 useful to avoid having to kill the capture
buffer manually. I assume that if
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:
> Edua
When loading the following file, I get:
'File mode specification error: (error Invalid base64 data)'
--- BEGIN SAMPLE FILE ---
#+STARTUP: inlineimages
#+begin_src org
[[attachment:thisfiledoesnotexist.jpg]]
#+end_src
--- END SAMPLE FILE ---
It also happens with 'begin_example'.
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.
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]]
This mail is related to 'Manual Ordering and Dynamic Priority' thread.
https://lists.gnu.org/archive/html/emacs-orgmode/2022-09/msg00091.html
Hi, I have just implemented an approach to creating a hierarchy of links to
tasks, so the hierarchy can be thought of a dependency tree (something like a
ting 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 phone numbers. Recent surveys indic
Based on my previous mail "Manual Ordering and Dynamic Priority" I would like
also to comment about this related idea.
In Agenda, it is possible to generate different views. I wonder whether it
would be possible to generate an "org mode" view. That is, a buffer in org-mode
format with all the
I have lots of tasks (todos) and I would like to create a long backlog based on
my perceived priority.
I was thinking to deal with them in the following way:
- divide them in groups (categories or similar),
- manually sort priority for every group,
- mergesort groups, that is, start merging
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
> **
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
:PROPERTIES:
:VISIBILITY: folded
:END:
ABAA
ABAB
ABAC
** AC
* B
* C
--- END ORG FILE
This works as
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
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
> > - Or
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>
> &g
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 have also tried without success:
- using begin_example,
- preceding with comma,
- special edit,
- starting the line with colon.
Any hint?
On the other
20 matches
Mail list logo
