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
"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
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 overri
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
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 u
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 a
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
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
>> "82388dff8ed006cecb65ea7a4afd
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
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
>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.
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
(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.
> 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
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 prop
> 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.
Total
> 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
or
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 sa
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 vide
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.i
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 com
>> 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
"Christopher M. Miles" writes:
> I meet an unfold-able headline now. Then I record a video to show this
> unfold-able headline. I executed command "describe-text-properties".
Please put the cursor right before the fold ("..."), execute M-x
describe-text-properties and share the properties descri
>
> 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 am in favor. One of my main problems in learning emacs: I started with e
Ag Ibragimov writes:
> Repro steps:
> ...
> Observed:
>
> It's wrapping the content into
> `(prn (binding [*out* (java.io.StringWriter.)]{:foo :bar}))`
>
> Expected:
>
> {:foo :bar}
I see the expected result on my side.
May you follow the steps starting from emacs -Q or make repro?
See https://o
"Christopher M. Miles" writes:
> 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-cloc
On 30/04/2023 17:39, Ihor Radchenko wrote:
Date: Mon, 3 Apr 2023 10:41:50 +0200
Subject: [PATCH v4 4/8] Use compat.el library instead of ad-hoc compatibility
function set
Ihor, I have not noticed removal of
;; `flatten-tree' was added in Emacs 27.1.
(defalias 'org-protocol-flatten
(if (fb
"Christopher M. Miles" writes:
> [[PGP Signed Part:Undecided]]
>
> 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
29 matches
Mail list logo
