Re: [POLL] Add command names to key bindings in Org Guide? (was: Suggestion: for each listed keybinding, also name the command)

[Adham Omran]

>> I want to add command names into the org-mode guide. I have attached
>> an example of such an addition.
>
> Will it be useful?
>
> Technically, adding the command name will increase the Org Guide size,
> which is a bit against its idea of compactness.

Wouldn't it just put additional information on the same line as the keybinding?

> On the other hand, new users may benefit from seeing the command names
> alongside with the bindings, especially users of pre-packages Emacs
> where the bindings may be shadowed by evil-mode and the likes.
>
> WDYT?

I think this would result in a more coherent experience between the manuals as 
the Emacs manual and Org mode manual both provide command names for most of the 
keybindings.

- Adham Omran

[FEATURE Request] inherit headline directory for `org-attach' in `org-add-note' etc temp buffers

[Christopher M. Miles]

For example, I have Org content like this:

#+begin_src org
,* TODO Refrigerator
DEADLINE: <2023-04-06 Thu>
:PROPERTIES:
:ID:   e1824d15-35cb-4105-a617-5f7ecd6a1049
:END:
#+end_src

I press [C-c C-z] `org-add-note` to add logbook note. It will open a new
temporary buffer. I want to execute command [C-c C-a m] `org-attach-mv`
to attach a file. But it will prompt me for org-attach directory. I
think commands like `org-add-note`, `org-clock` add log, `org-todo`
change TODO state add log, etc should auto inherit this org-attach
directory. So that user can do `org-attach` in the temporary log buffer.

WDYT?

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature

[BUG] Tangling of clojure code blocks is broken [9.7 (9.7-??-0807107 @ /Users/ag/.emacs.d/.local/straight/build-30.0.50/org/)]

[Ag Ibragimov]

Tangling Clojure code blocks appear to be broken.

Repro steps:

- Create a Clojure source block, e.g., 

#+begin_src clojure :tangle foo.clj
{:foo :bar}
#+end_src

- Tangle it, M-x org-babel-tangle

- Check the file content

Observed:

It's wrapping the content into
`(prn (binding [*out* (java.io.StringWriter.)]{:foo :bar}))`

Expected:

{:foo :bar}





Emacs  : GNU Emacs 30.0.50 (build 1, aarch64-apple-darwin22.4.0, NS 
appkit-2299.50 Version 13.3.1 (Build 22E261))
 of 2023-04-27
Package: Org mode version 9.7 (9.7-??-0807107 @ 
/Users/ag/.emacs.d/.local/straight/build-30.0.50/org/)

Re: BUG: org-cycle does not unfold some subtrees

[Christopher M. Miles]

I meet an unfold-able headline now. Then I record a video to show this
unfold-able headline. I executed command "describe-text-properties".
Afterwards, I closed the buffer, then re-open the file to show the
headline can be expanded normally, and show the subtree content.

Here is the uploaded video (P.S, I know video link is not a good way to
archive information in mailing list, but this problem seems can't be
text-described simply. Sorry about this.):

https://upload.disroot.org/r/QNhW1xz0#X2or/2T7i7Kb7pHPxfAupRaEYJ28Sbp+2R6UDREnFic=

Ihor Radchenko  writes:

> Michael Dauer  writes:
>
>> This is with the cursor on the first asterisk:
>> Text content at position 299:
>>
>>
>> There are text properties here:
>>   display  [Show]
>>   face org-level-1
>>   fontifiedt
>
> Well. This shows nothing.
> I am more interested in text properties at the fold.
>
>> I could not test more positions because I accidentally cut it, and even an
>> undo fixed it. I would have to wait until it happens again.
>
> Sure. Let me know when you are able to get more info.


-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature

Re: BUG: org-cycle does not unfold some subtrees

[Christopher M. Miles]

Michael Dauer  writes:

> Maybe I missed a known bug when doing the research. But all the other reports 
> describe different and
> reproducible behaviour.
>
> Sometimes (often) I cannot unfold a subtree. It then affects only one or more 
> subtrees while others in the
> same buffer or even the same branch still work. The only fix then is to 
> either cut and paste the affected
> branches, or to close and reopen the file.
>
> While quite frequent I have not achieved to reproduce the issue. It just 
> happens after a while of using
> multiple files navigating with search, tab from agenda, org-refile, and cycle.
>
> Based on my analyses it's not the cycle functions, but must come from broken 
> text attributes. Even
> (org-fold-core-region (point-min) (point-max) nil) does not unfold the 
> affected subtrees then. Assuming
> that (org-fold-core-region) is the only place where the folding and hiding 
> happens, I expect the problem
> there. But I understand too little about the emacs internals to debug this 
> function.
>
> I hope this helps to fix the issue.
>
> Org mode version 9.7-pre (release_9.6.4-327-gf81ba4

I got same problem many times. Usually I close buffer and re-open file again.
I can confirm this issue. I will provides some info help here too.

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Karthik Chikmagalur]

> The preview now works as stated, although I find it kinda slow to
> regenerate, even if I set `org-latex-preview-throttle' to 0.2.

They shouldn't be any slower than when you manually call
`org-latex-preview' on a fragment.  To be sure, you could try

(setq org-latex-preview-debounce 0.3
  org-latex-preview-throttle 0.3)

and then turn on (or turn off + on) `org-latex-preview-auto-mode'.

> Also for some reason my previews appear to the right of the cursor,
> instead of under it like in the linked webm.

The video you linked to was a proof of concept.  Here is a demo of the
current design: https://tinyurl.com/ms2ksthc

If `org-latex-preview-live-display-type' is set to `eldoc':
- show live previews using Eldoc.  You may need to pop up the Eldoc doc
buffer for larger previews to be visible (`M-x eldoc-mode', followed by
`M-x eldoc-doc-buffer').

Else:
- Inline fragments are live-previewed inline
- LaTeX environments are previewed below the environment

> My last problem is that exports are kinda borked. For example, these
> days I started using `org-msg' and when my email exports to html and
> latex is included, one of these happen:
>
> - The fragment appears as a blank image when the options `tex:dvipg' or
>   `tex:dvisvg' are used.
> - The email doesn't even export to html with a message like
>   `org-html-latex-image: Expected LaTeX preview
> "424ed928d1eaca9e3c4c588469a4a0b87a7f4329" to exist in the cache'
>   with the option `tex:imagemagick'.

Tecosaur will have a better idea of what's happening here.  Note that
the export options for html are `tex:dvipng' or `tex:dvisvgm', not
`dvipg' and `dvisvg'.

>> If the live preview is not removed automatically after you move away
>> from a LaTeX fragment, you might have to manually eval
>> `(org-latex-preview-live--clearout)'.
>
> Yeah, it happens to me to. Even if I remove the fragment the preview
> persists.

It shouldn't be happening every time -- only when certain conditions are
met.  Deleting fragments might be one of these conditions.

-Karthik

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Konstantinos Chousos]

> Is tooltip-mode turned on?

That was it! Thank you so much! Now both error messages and live
previews work!

> We'd like to focus on improving the user experience of the core features
> first.  If these issues are cleaned up before 9.7, I will work on
> polishing the live previews feature.

Totally agree. It should only be merged when its ready.


> There is no documentation for live-previews yet.  If you would like
> to try it -- and I encourage you to -- you could set:
>
> (setq org-latex-preview-auto-generate 'live)
>
> and then turn on `org-latex-preview-auto-mode'.  The variables
> `org-latex-preview-throttle' and `org-latex-preview-debounce' control
> the responsiveness of the live previews.

The preview now works as stated, although I find it kinda slow to
regenerate, even if I set `org-latex-preview-throttle' to 0.2. Also for
some reason my previews appear to the right of the cursor, instead of
under it like in the linked webm.

My last problem is that exports are kinda borked. For example, these
days I started using `org-msg' and when my email exports to html and
latex is included, one of these happen:

- The fragment appears as a blank image when the options `tex:dvipg' or
  `tex:dvisvg' are used.
- The email doesn't even export to html with a message like
  `org-html-latex-image: Expected LaTeX preview
"424ed928d1eaca9e3c4c588469a4a0b87a7f4329" to exist in the cache'
  with the option `tex:imagemagick'.

> If the live preview is not removed automatically after you move away
> from a LaTeX fragment, you might have to manually eval
> `(org-latex-preview-live--clearout)'.  This is one of the many edge
> cases with the feature that need to be handled.

Yeah, it happens to me to. Even if I remove the fragment the preview
persists.


Thanks for your quick reply. All the best.

--Konstantinos

Re: BUG: org-cycle does not unfold some subtrees

[Ihor Radchenko]

Michael Dauer  writes:

> This is with the cursor on the first asterisk:
> Text content at position 299:
>
>
> There are text properties here:
>   display  [Show]
>   face org-level-1
>   fontifiedt

Well. This shows nothing.
I am more interested in text properties at the fold.

> I could not test more positions because I accidentally cut it, and even an
> undo fixed it. I would have to wait until it happens again.

Sure. Let me know when you are able to get more info.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Karthik Chikmagalur]

> 1. Use TEC's org-mode =dev= branch, up to the =---NOPUSH PERSONAL
>DIVIDER---= commit.
> 2. Set some config options, which can be in the above link.
> 3. Test the new features.
> 4. When a latex fragment contained an error, its color would turn red,
>but no popup would appear on hover, or ever for that matter.
>
>My temporary solution is to directly check the =*Org Preview LaTeX
>Output*= buffer.

Is tooltip-mode turned on?

>> We don't think live previews will be ready or stable enough in time
>> for Org 9.7, so it is not currently part of the patch set.
>
> That's too bad, it looked really neat and useful.

We'd like to focus on improving the user experience of the core features
first.  If these issues are cleaned up before 9.7, I will work on
polishing the live previews feature.

>> It's available as a later WIP (work in progress) commit on
>> tecosaur's dev branch, if you are interested in trying it.
>
> I noticed that but as I said above, I already use that branch. Perhaps
> the bug with the error popups and this are related? After all, both have
> to do with popups. Also it is important to note that I have already set
> the configuration variables that are relevant to the /live/ preview (at
> least those that I could find).

There is no documentation for live-previews yet.  If you would like
to try it -- and I encourage you to -- you could set:

(setq org-latex-preview-auto-generate 'live)

and then turn on `org-latex-preview-auto-mode'.  The variables
`org-latex-preview-throttle' and `org-latex-preview-debounce' control
the responsiveness of the live previews.

If the live preview is not removed automatically after you move away
from a LaTeX fragment, you might have to manually eval
`(org-latex-preview-live--clearout)'.  This is one of the many edge
cases with the feature that need to be handled.

> All in all this is a huge improvement and a quality-of-life upgrade for
> all org-mode users. Thank you both for your work.

Thank you! The testing is very helpful as well.

-Karthik

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Konstantinos Chousos]

(Don't mind the mail change, still the same guy. Just started dabbling
in email in Emacs and gmail works better for that).

> From your diagnostic report, it looks like you're using lualatex +
> precompilation.  This can cause some issues, but not the ones you
> report above so this is interesting.

If I remember correctly, when I run the test I had precompilation turned
off, because with it =lualatex= didn't work, but the diagnostics kept
thinking it was on. Even so, it is currently disabled.

>> 1. When a snippet contains a mistake, it correctly turns red, but no
>> error message is shown when I hover my mouse over it. I have to
>> switch to the *Org Preview LaTeX Output* to see the error.
>
> This is a bug, could you list the steps to reproduce it?

All my relevant configuration was attached in my previous message. If it
helps, my complete Emacs configuration resides at
https://github.com/kchousos/Emacs/blob/master/Emacs.org. The only
noteworthy thing I can think of is that i use Wayland. Also, my Emacs'
version is =29.0.90= and found at
https://copr.fedorainfracloud.org/coprs/majore-biscuit/Emacs-29/. After
that, the steps were the following:

1. Use TEC's org-mode =dev= branch, up to the =---NOPUSH PERSONAL
   DIVIDER---= commit.
2. Set some config options, which can be in the above link.
3. Test the new features.
4. When a latex fragment contained an error, its color would turn red,
   but no popup would appear on hover, or ever for that matter.

   My temporary solution is to directly check the =*Org Preview LaTeX
   Output*= buffer.

> We don't think live previews will be ready or stable enough in time
> for Org 9.7, so it is not currently part of the patch set.

That's too bad, it looked really neat and useful.

> It's available as a later WIP (work in progress) commit on
> tecosaur's dev branch, if you are interested in trying it.

I noticed that but as I said above, I already use that branch. Perhaps
the bug with the error popups and this are related? After all, both have
to do with popups. Also it is important to note that I have already set
the configuration variables that are relevant to the /live/ preview (at
least those that I could find).


All in all this is a huge improvement and a quality-of-life upgrade for
all org-mode users. Thank you both for your work.

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Konstantinos Chousos]

Re: BUG: org-cycle does not unfold some subtrees

[Michael Dauer]

This is with the cursor on the first asterisk:
Text content at position 299:


There are text properties here:
  display  [Show]
  face org-level-1
  fontifiedt

I could not test more positions because I accidentally cut it, and even an
undo fixed it. I would have to wait until it happens again.

Am Fr., 5. Mai 2023 um 19:43 Uhr schrieb Ihor Radchenko :

> Michael Dauer  writes:
>
> > Based on my analyses it's not the cycle functions, but must come from
> > broken text attributes. Even (org-fold-core-region (point-min)
> (point-max)
> > nil) does not unfold the affected subtrees then. Assuming that
> > (org-fold-core-region) is the only place where the folding and
> > hiding happens, I expect the problem there. But I understand too little
> > about the emacs internals to debug this function.
>
> May you please put a point right before the problematic fold, run
> M-x describe-text-properties , and share the contents of the newly
> displayed buffer listing all the text properties?
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>

Re: [Pre-PATCH] Overhaul of the LaTeX preview system

[Karthik Chikmagalur]

>From your diagnostic report, it looks like you're using lualatex +
precompilation.  This can cause some issues, but not the ones you report
above so this is interesting. 

> 1. When a snippet contains a mistake, it correctly turns red, but no
> error message is shown when I hover my mouse over it. I have to switch
> to the *Org Preview LaTeX Output* to see the error.

This is a bug, could you list the steps to reproduce it?

> 2. Live previews do not work (like shown here
> https://tinyurl.com/5fu7z27w), although I am using the related options
> and use your branch up to the ---PATCH SET DIVIDER--- commit.

We don't think live previews will be ready or stable enough in time for
Org 9.7, so it is not currently part of the patch set.  It's available
as a later WIP (work in progress) commit on tecosaur's dev branch, if
you are interested in trying it.

> 4. Some key-binds (like C-c C-e to publish or C-c C-x C-l for
> latex-preview) do not work when the cursor is at the top of the file,
> before the first header.

This is also a bug, thanks for the report.  I'll look into it.

-Karthik

Re: BUG: org-cycle does not unfold some subtrees

[Ihor Radchenko]

Michael Dauer  writes:

> Based on my analyses it's not the cycle functions, but must come from
> broken text attributes. Even (org-fold-core-region (point-min) (point-max)
> nil) does not unfold the affected subtrees then. Assuming that
> (org-fold-core-region) is the only place where the folding and
> hiding happens, I expect the problem there. But I understand too little
> about the emacs internals to debug this function.

May you please put a point right before the problematic fold, run
M-x describe-text-properties , and share the contents of the newly
displayed buffer listing all the text properties?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

BUG: org-cycle does not unfold some subtrees

[Michael Dauer]

Maybe I missed a known bug when doing the research. But all the other
reports describe different and reproducible behaviour.

Sometimes (often) I cannot unfold a subtree. It then affects only one or
more subtrees while others in the same buffer or even the same branch still
work. The only fix then is to either cut and paste the affected branches,
or to close and reopen the file.

While quite frequent I have not achieved to reproduce the issue. It just
happens after a while of using multiple files navigating with search, tab
from agenda, org-refile, and cycle.

Based on my analyses it's not the cycle functions, but must come from
broken text attributes. Even (org-fold-core-region (point-min) (point-max)
nil) does not unfold the affected subtrees then. Assuming that
(org-fold-core-region) is the only place where the folding and
hiding happens, I expect the problem there. But I understand too little
about the emacs internals to debug this function.

I hope this helps to fix the issue.

Org mode version 9.7-pre (release_9.6.4-327-gf81ba4

Re: [EasyPG (epa)] Emacs can't save modified encrypted file

[Christopher M. Miles]

Ihor Radchenko  writes:

> "Christopher M. Miles"  writes:
>
>> - [X] Then I check out Emacs source code file "epg.el" & "epa.el" file
>>   git log. -> have not found obvious gpg command-line options related to
>>   the problem. One small possible commit might be
>>   "82388dff8ed006cecb65ea7a4afd8667ec44b5e3".
>
> One of the reddit comments mentioned that the newer gpg hangs when not
> provided input. If this is true, I notice that `epg-start-encrypt' first
> calls (epg-wait-for-status context '("BEGIN_SIGNING")) and only then
> sends the buffer string for encryption (process-send-string).

In order to connect this mail list thread with the Emacs bug report.
Put bug report link here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63256

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature

Re: [POLL] Add command names to key bindings in Org Guide?

[Ihor Radchenko]

Esteban Ordóñez  writes:

> I think that mentioning command names would help a lot to understand the
> objective of the command and would also help to find its documentation. 
> A common problem for me was [is?] that I could not find the place where
> there is more information about something.  The size of the document is
> not as important, if it is easy to find your way in it.

Let me clarify a bit: size of Org Guide specifically is important.
We already have command names with appropriate searchable index entries
in the main manual. But Org Guide is intended for newbies as a place to
get started:

This document is a much compressed derivative of the comprehensive Org
mode manual.  It contains all basic features and commands, along with
important hints for customization.  It is intended for beginners who
would shy back from a 200 pages manual because of sheer size.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [POLL] Add command names to key bindings in Org Guide?

[Esteban Ordóñez]

El 2023-05-05 06:01, Ihor Radchenko escribió:
> Yuval Langer  writes:
> 
>> For many commands, I find it helpful to first learn their names before
>> learning their keybindings. The org-mode guide does not include
>> command names.
>>
>> I want to add command names into the org-mode guide. I have attached
>> an example of such an addition.
> 
> Will it be useful?
> 
> Technically, adding the command name will increase the Org Guide size,
> which is a bit against its idea of compactness.
> 
> On the other hand, new users may benefit from seeing the command names
> alongside with the bindings, especially users of pre-packages Emacs
> where the bindings may be shadowed by evil-mode and the likes.
> 
> WDYT?

I think that mentioning command names would help a lot to understand the
objective of the command and would also help to find its documentation. 
A common problem for me was [is?] that I could not find the place where
there is more information about something.  The size of the document is
not as important, if it is easy to find your way in it.

[POLL] Add command names to key bindings in Org Guide? (was: Suggestion: for each listed keybinding, also name the command)

[Ihor Radchenko]

Yuval Langer  writes:

> For many commands, I find it helpful to first learn their names before
> learning their keybindings. The org-mode guide does not include
> command names.
>
> I want to add command names into the org-mode guide. I have attached
> an example of such an addition.

Will it be useful?

Technically, adding the command name will increase the Org Guide size,
which is a bit against its idea of compactness.

On the other hand, new users may benefit from seeing the command names
alongside with the bindings, especially users of pre-packages Emacs
where the bindings may be shadowed by evil-mode and the likes.

WDYT?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Suggestion: for each listed keybinding, also name the command

[Yuval Langer]

For many commands, I find it helpful to first learn their names before
learning their keybindings. The org-mode guide does not include
command names.

I want to add command names into the org-mode guide. I have attached
an example of such an addition.

The changes in the first commit might be later dropped as it
might be better to add command names only in the command lists.

This addition might not be appropriate for the org-mode guide, as it
is already covered by the org-mode manual, but I would have found it
very useful if the names of the commands were included.
From c03d821a9726e203113d622d1581a02d32b75302 Mon Sep 17 00:00:00 2001
From: Yuval Langer 
Date: Fri, 5 May 2023 11:57:37 +0300
Subject: [PATCH 1/2] Add first function names.

---
 doc/org-guide.org | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/org-guide.org b/doc/org-guide.org
index 95828e4c0..3581e0a5e 100644
--- a/doc/org-guide.org
+++ b/doc/org-guide.org
@@ -141,7 +141,8 @@ See [[*Miscellaneous]] for a setup to realize this.
 
 Outlines make it possible to hide parts of the text in the buffer.
 Org uses just two commands, bound to {{{kbd(TAB)}}} and
-{{{kbd(S-TAB)}}} to change the visibility in the buffer.
+{{{kbd(S-TAB)}}} (~org-cycle~ and ~org-shifttab~) to change the
+visibility in the buffer.
 
 #+attr_texinfo: :sep ,
 - {{{kbd(TAB)}}} ::
-- 
2.30.2

From 08cadefe808c00e186991feec0f66e141a720986 Mon Sep 17 00:00:00 2001
From: Yuval Langer 
Date: Fri, 5 May 2023 12:38:07 +0300
Subject: [PATCH 2/2] Add names to a few list entries.

---
 doc/org-guide.org | 22 --
 1 file changed, 12 insertions(+), 10 deletions(-)

diff --git a/doc/org-guide.org b/doc/org-guide.org
index 3581e0a5e..3747e2d68 100644
--- a/doc/org-guide.org
+++ b/doc/org-guide.org
@@ -145,7 +145,7 @@ Org uses just two commands, bound to {{{kbd(TAB)}}} and
 visibility in the buffer.
 
 #+attr_texinfo: :sep ,
-- {{{kbd(TAB)}}} ::
+- {{{kbd(TAB)}}} (~org-cycle~) ::
 
   /Subtree cycling/: Rotate current subtree among the states
 
@@ -155,7 +155,7 @@ visibility in the buffer.
   When called with a prefix argument ({{{kbd(C-u TAB)}}}), or with the
   Shift key, global cycling is invoked.
 
-- {{{kbd(S-TAB)}}}, {{{kbd(C-u TAB)}}} ::
+- {{{kbd(S-TAB)}}} (~org-shifttab~), {{{kbd(C-u TAB)}}} ::
 
   /Global cycling/: Rotate the entire buffer among the states
 
@@ -181,15 +181,17 @@ basis by adding a =STARTUP= keyword to =overview=, =content=,
 
 The following commands jump to other headlines in the buffer.
 
-- {{{kbd(C-c C-n)}}} :: Next heading.
-
-- {{{kbd(C-c C-p)}}} :: Previous heading.
+- {{{kbd(C-c C-n)}}} (~org-next-visible-heading~) :: Next heading.
+- {{{kbd(C-c C-p)}}} (~org-previous-visible-heading~) :: Previous
+  heading.
 
-- {{{kbd(C-c C-f)}}} :: Next heading same level.
+- {{{kbd(C-c C-f)}}} (~org-backward-heading-same-level~):: Next
+  heading same level.
 
-- {{{kbd(C-c C-b)}}} :: Previous heading same level.
+- {{{kbd(C-c C-b)}}} (~outline-backward-same-level~) :: Previous
+  heading same level.
 
-- {{{kbd(C-c C-u)}}} :: Backward to higher level heading.
+- {{{kbd(C-c C-u)}}} (~outline-up-heading~) :: Backward to higher level heading.
 
 ** Structure Editing
 :PROPERTIES:
@@ -197,14 +199,14 @@ The following commands jump to other headlines in the buffer.
 :END:
 
 #+attr_texinfo: :sep ,
-- {{{kbd(M-RET)}}} ::
+- {{{kbd(M-RET)}}} (~org-meta-return~) ::
 
   Insert new heading with same level as current.  If point is in
   a plain list item, a new item is created (see [[Plain Lists]]).  When
   this command is used in the middle of a line, the line is split and
   the rest of the line becomes the new headline[fn:2].
 
-- {{{kbd(M-S-RET)}}} ::
+- {{{kbd(M-S-RET)}}} (~org-insert-todo-heading~) ::
 
   Insert new TODO entry with same level as current heading.
 
-- 
2.30.2

Re: [PATCH] epm.el: A CLI tool for package.el

[Ihor Radchenko]

Max Nikulin  writes:

> Do you have any arguments against switching from emacs -Q to emacs -q? I 
> am still unsure if it is safe enough, but not doing it is not better. I 
> am considering adding -q to this script when it is called directly. 
> Unfortunately Emacs does not have an option to override effect of -q.

Given that --batch implies -q, it should be relatively safe. Maybe
except make repro, where we want to minimize environment effects.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [EasyPG (epa)] Emacs can't save modified encrypted file

[Ihor Radchenko]

"Christopher M. Miles"  writes:

> - [X] Then I check out Emacs source code file "epg.el" & "epa.el" file
>   git log. -> have not found obvious gpg command-line options related to
>   the problem. One small possible commit might be
>   "82388dff8ed006cecb65ea7a4afd8667ec44b5e3".

One of the reddit comments mentioned that the newer gpg hangs when not
provided input. If this is true, I notice that `epg-start-encrypt' first
calls (epg-wait-for-status context '("BEGIN_SIGNING")) and only then
sends the buffer string for encryption (process-send-string).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [EasyPG (epa)] Emacs can't save modified encrypted file

[Christopher M. Miles]

Ihor Radchenko  writes:

> Some more info: 
> https://old.reddit.com/r/emacs/comments/137r7j7/gnupg_241_encryption_issues_with_emacs_orgmode/

Indeed same problem as mine. Thanks Ihor

- [X] *downgrade* GnuPG from 2.4.1 -> 2.4.0 temporary get around the problem.

  #+begin_src sh
  brew info gnupg | grep "From:" | cut -d " " -f 2
  #+end_src

  #+RESULTS[(2023-05-05 14:19:54) 0e3dbbad14b66a4f05d2d70fb5cfd59db46f49bc]:
  : https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/gnupg.rb

  #+begin_src sh
  
URL=https://raw.githubusercontent.com/Homebrew/homebrew-core/59edfe598541186430d49cc34f42671e849e2fc9/Formula/gnupg.rb
  wget $URL
  brew uninstall gnupg
  brew install -s gnupg.rb
  #+end_src

- [X] Check out GnuPG homepage changelog, Found new feature "ADSK: The 
Additional Decryption Subkey" for the problem gnupg version "2.4.1".
  After I executed bellowing command, -->> I still has problem.
  https://www.gnupg.org/blog/20230321-adsk.html

  #+begin_src sh
  gpg -K --with-subkey-fingerprint stardiviner
  #+end_src

  #+RESULTS[(2023-05-05 14:44:34) bc8e7497ce39ff0a8ae3fc45c332d64685e8da46]:
  : sec   rsa2048 2015-01-31 [SC]
  :   F09F650D7D674819892591401B5DF1C95AE89AC3
  : uid   [ultimate] stardiviner (numbch...@gmail.com) 

  : uid   [ultimate] stardiviner (Christopher Miles) 

  : uid   [ultimate] [jpeg image of size 3384]
  : ssb   rsa2048 2015-01-31 [E]
  :   32A8581A6E137ABD26DA2F570251FA6886EB6B77
  : 

  #+begin_src sh
  gpg --quick-add-adsk F09F650D7D674819892591401B5DF1C95AE89AC3 
32A8581A6E137ABD26DA2F570251FA6886EB6B77
  #+end_src

- [X] Then I check out Emacs source code file "epg.el" & "epa.el" file
  git log. -> have not found obvious gpg command-line options related to
  the problem. One small possible commit might be
  "82388dff8ed006cecb65ea7a4afd8667ec44b5e3".

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without 
misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3


signature.asc
Description: PGP signature