Problem with installation

Hi, I execute in kubuntu 22.04: > git clone https://git.savannah.gnu.org/git/emacs/org-mode.git > cd org-mode > make autoloads and get the messages: == = Invoke "make help" for a synopsis of make targets. = = Created a default local.mk templa

Re: Problem with installation

anilomjf writes: > Hi, > > I execute in kubuntu 22.04: > >> git clone https://git.savannah.gnu.org/git/emacs/org-mode.git >> cd org-mode >> make autoloads > > and get the messages: > ... > Loading /home/javi/org-mode/lisp/org-compat.el (source)... > Eager macro-expansion failure: (file-missing "

Re: Problem with installation

[ Adding the org mailing list back to the CC ] anilomjf writes: > Thank you for your rapid response. > > My emacs version is 27.1 I tested using Emacs 27.2 on Gentoo Linux using your exact steps. Still unable to reproduce. Best, Ihor

Re: Problem with installation

[ Adding the org mailing list back to the CC ] anilomjf writes: > Here: > > https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development > > > > It is stated that: > > Yes. You can install org-latest.zip or > org-latest

Re: Problem with installation

anilomjf writes: > Shoud org-version be in the lisp directory when I clone the repository? > > It is not. org-version.el should be generated by make script. Best, Ihor

Re: per-file (or, really, per buffer) allowing/disallowing code block execution

Hello Richard, Ihor and Steven, I'm aware that file-local variables exist, but it seems that all documentation for them put them *into the file*, which is not secure for files downloaded from the internet. What is to stop a malicious file from setting an "yes, execute me automatically" variable?

Re: [PATCH v2] org.el: Preserve case for link subgroups from `org-file-apps'

On 06/09/2022 19:07, Ihor Radchenko wrote: Max Nikulin writes: Debugging `org-file-apps' and `org-open-file' regexp subgroups I noticed an issue: the code distorts case of the link components making them invalid. The patch to fix the bug is attached, the commit message contains an example of th

Org mode "style sheet" for software documentation

I don’t understand this page: https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers In particular, the BORDER BODY BORDER part. Note that this is the CONTENT which is already between MARKERS. What I *think* I want is the

Re: per-file (or, really, per buffer) allowing/disallowing code block execution

On Thu, Sep 08, 2022 at 12:34:25PM +, Fedja Beader wrote: > Hello Richard, Ihor and Steven, > > I'm aware that file-local variables exist, but it seems that > all documentation for them put them *into the file*, which is not secure for > files downloaded from the internet. What is to stop a m

Re: [PATCH] ox-icalendar.el: customizable vevent summary prefix

Thank you for suggestion, I seen an announcement about this function, but somehow forgot about it. Sending next version of these patches. Changes from the next version: • Removed my version of title gathering into one existing in org-clock.el • Split org-clock-get-file-title renaming into separa

Re: Org mode "style sheet" for software documentation

> On Sep 8, 2022, at 11:20, Perry Smith wrote: > > I don’t understand this page: > https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers > > > In particular, the BORDER BODY BORDER part. Note that this is the CONTENT >

Re: Org mode "style sheet" for software documentation

Perry Smith writes: > So… it seems I didn’t the two BORDER characters do not need to match. So I’m > off trying to figure out a way to create more emphasis MARKERS. In the old > days, we had only about 43 non-alphanumeric characters to play with but now > with Emacs being 8 bit clean for cou

Re: per-file (or, really, per buffer) allowing/disallowing code block execution

Fedja Beader writes: > I'm aware that file-local variables exist, but it seems that > all documentation for them put them *into the file*, which is not secure for > files downloaded from the internet. What is to stop a malicious file from > setting an "yes, execute me automatically" variable?

Why do org-agenda-switch-to and org-agenda-goto put the point in different spots in the target buffer?

I've gotten back into using org-agenda to manage my todos, and I noticed an odd discrepancy in behavior. When I hit RET in the agenda buffer to go to the TODO entry in the original org file, I see that the point is on the DEADLINE line. However, when I hit TAB, I find that the point is placed at

[BUG] org-catch-invisible-edits has stopped working [9.5.5 (9.5.5-geb5ef0 @ /home/slk/.emacs.default/straight/build/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. --