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

[Rohit Patnaik]

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 the beginning of 
the heading. Looking at the source of org-agenda.el, I find that TAB is bound 
to `org-agenda-goto', which does the following:

(recenter (/ (window-height) 2))
(org-back-to-heading t)

RET, on the other hand, is bound to `org-agenda-switch-to', which does not have 
these lines, and thus does not place the point on the heading.

Is there a reason for this discrepancy between the two functions? I'm asking 
because I prefer the point placement behavior of `org-agenda-goto', but I use 
`org-agenda-switch-to' because switches to the target org file in the current 
window rather than opening a new window. Would there be any issues with me 
taking the recentering and point placement behavior from `org-agenda-goto' and 
adding it to `org-agenda-switch-to`?

Thanks,
Rohit

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

[Ihor Radchenko]

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?

As Tomas pointed out, Emacs has a concept of safe and non-safe
file-local variables. org-confirm-babel-evaluate in particular is only
safe when it is set to t (query execution). If your downloaded file
attempts to set org-confirm-babel-evaluate to nil, Emacs will show a
warning and ask you whether you want to use this unsafe nil value.

> Anyway, the point of my email was to suggest a change to org-mode such that 
> it provides a pleasant out-of-the-box user experience for people like me. I 
> want to use org-mode as a python/octave/R/whatever interactive notebook 
> without having to spend several days learning elisp and the internal workings 
> of Emacs. I have spent these days, days that could be better (sorry!) used 
> working on actual projects of mine. But I spent this time and the time to 
> articulate what I want and to write these emails in the hope that I will be 
> the last person having to do so. I would also like to suggest org-mode to 
> other people instead of Jupyter notebook without having to add "oh, btw, you 
> might want to add these three pages of alien code to your init.el to make it 
> usable".

I am sorry if any of the answers to your suggestion sounded hostile.
Note that Org mode already has a large number of customizations, which
is why we are trying to not introduce unnecessary customizations. Too
many options is not always a good thing.

The above does not mean that we reject your suggestion. Rather we try to
weigh on the available options in Org and Emacs itself and then try to
integrate the new feature into the existing concepts/functionalities.

> To go a bit further off-thread, this change might seem unnecessary. However, 
> the other changes I want is also auto-executing all modified code blocks on 
> file save and/or when the cursor moves out of it, auto-executing dependent 
> blocks when their dependency changes (e.g. blocks full of constants) or 
> marking blocks as stale. But I will make suggestions to improve these things 
> in later emails, once I know what I want.

Feel free to do so. Suggestions are always welcome.

> Hello Ihor,
>
>> Then, what about the following:
>> 1. Set org-confirm-babel-evaluate globally to t
>> 2. In the files you maintain, you can always put
>>file-local/directory-local value of org-confirm-babel-evaluate to
>>nil.
>> 3. We can modify org-babel-confirm-evaluate _function_ to accept four
>>possible answers: yes, no, yes for all in buffer, no for all in
>>buffer. The extra 2 options will set buffer-local value of
>>org-confirm-babel-evaluate in the current Emacs session
>
> Don't know about option (1), (2) seems insecure at first glance, for the 
> reasons mentioned above. (3) sounds good (yes/no/always/never?) and what I 
> want.

(1) is what Org uses by default. I mentioned it just in case if you have
org-confirm-babel-evaluate set to nil. (Many people do use this unsafe
setting).

(2) Is safe because file-local nil value of org-confirm-babel-evaluate
will trigger Emacs to show you a warning, as I described earlier.

(3) Let me elaborate a bit.

Yes-for-all/No-for-all may be implemented in multiple ways:
- During the current org-babel-execute-buffer call
- From now until the buffer is closed
- Forever for this file path
- Forever for this file path until the file contents is changed
- For some period of time

Moreover, the above may apply for all the src blocks in buffer or just a
particular src block.

I doubt that all the options should be implemented in practice. We may
probably just allow yes-for-all when running org-babel-execute-buffer
but not individual C-c C-c on src blocks. I can see valid reasons to
allow (1) in current org-babel-execute-buffer-call; (2) until the buffer
is closed; (3) until the file contents is changed + limited by time.
However, 3 possible options in the dialogue may be disorienting:

yes/no (each src block)
Yes/No (all src blocks in current org-babel-execute-buffer cal)
* (until the buffer is closed)
! (until the buffer is closed and in the next 30 days, as long as the
  buffer contents is not changed)

WDYT?

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

Re: Org mode "style sheet" for software documentation

[Ihor Radchenko]

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 countless years we have another 128 
> characters and with UTF-8 we have bazillians more!
>
> So I’m gently poking around in the code to see how hard it would be to define 
> more.

We currently do not support extensions to emphasis, though we may do it
in future. See https://orgmode.org/list/87letvrege.fsf@localhost

Implementing new emphasis markers will require introducing a new syntax
object into org-element.el. Such object will unlikely be using a
single-char markers - single-char markers are problematic in numerous
edge cases; we should better introduce something closer to inline src
block syntax to allow arbitrary emphasis extensions.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

Re: Org mode "style sheet" for software documentation

[Perry Smith]

> 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 
> which is already between MARKERS.
> 
> What I *think* I want is the ability to effectively create what I’ll call 
> “macros”.  I’d like to be able to separate out things like file paths, code 
> samples (both in line and block), keywords, environment variables, code 
> variables, etc.  So, as I write, I would do (as a total pretend example) 
> [var]foo_dog[var] to denote foo_dog as a code variable.  I’m wondering if 
> that isn’t what the “BORDER” character is.  From the way the section is 
> written, I would assume the leading border character must be the same as the 
> trailing border character so I could do ~vfoo_docv~  where the “v” would be 
> the border character?
> 
> OR… perhaps what this is trying to tell me is the first character after the 
> leading marker and the last character before the trailing marker must not be 
> whitespace characters since that is how it appears from all of the examples.
> 
> My logic is if I take the time to separate out all of the elements as I write 
> the document, then I can later decide to format, for example, code snippets 
> the same as variables.  It would also help me to be more consistent while I 
> write because I’m (currently) having to remember “Ok… how did I format 
> variables?  Was that ‘code' or ‘italics'? … Hmm…”
> 
> If I’ve misunderstood this page, then perhaps to save a follow up email, can 
> someone tell me if I can create “macros” within Org mode to do what I 
> mentioned OR tell me that I really don’t want to go down that path for some 
> reason.

From the code:
Terminology:  In an emphasis string
like " *strong word* ", we call the initial space PREMATCH, the final
space POSTMATCH, the stars MARKERS, "s" and "d" are BORDER characters
and "trong wor" is the body.

The code has clearer documentation than the documentation :-)

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 countless years we have another 128 characters 
and with UTF-8 we have bazillians more!

So I’m gently poking around in the code to see how hard it would be to define 
more.

pedz



signature.asc
Description: Message signed with OpenPGP

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

[Mikhail Skorzhisnkii]

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 separate commit
• More grammar and wording fixes in changelogs

  Thanks,
  Mikhail

Ihor Radchenko  writes:

> Mikhail Skorzhisnkii  writes:
>
>>> Also, what will happen in a file like
>>>
>>> #+TITLE: Begin title
>>> #+TITLE: .. end title
>>>
>>> ?
>>
>> Hm, never did this myself. Now concatenate the list of property values. I 
>> have
>> tested it and space as a separator looks good, if the intention of several
>> titles is to have one big title.
>>
>> But what if several titles are title and subtitles? We can provide a way 
>> control
>> that behaviour, but my gut feeling that it would be a rather confusing.
>
> See org-clock-get-file-title. You can move that function into org.el and
> rename to org-get-file-title.
>From 47c61b597a3064755964d763621616d184c351ad Mon Sep 17 00:00:00 2001
From: Mikhail Skorzhinskii 
Date: Mon, 21 Sep 2020 14:53:13 +0200
Subject: [PATCH 3/3] org-refile.el: show refile targets with a title

* lisp/org-refile.el (org-refile-get-targets): Use a document
title (#+TITLE) instead of file or buffer name in outline path, if
a corresponding customisation option is set to 'title. Fallback to a
filename if there is no title in the document.
* lisp/org-refile.el (org-refile-use-outline-path): Add a new option
'title, see above
---
 etc/ORG-NEWS |  6 ++
 lisp/org-refile.el   | 17 ++---
 testing/lisp/test-org.el | 37 -
 3 files changed, 56 insertions(+), 4 deletions(-)

diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 8f57d252f..cc63b679d 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -295,6 +295,12 @@ Use the header argument =:var x=code-block[]= or
 to pass the contents of a named code block as a string argument.
 
 ** New options
+*** A new option for custom setting =org-refile-use-outline-path= to show document title in refile targets
+
+Setting =org-refile-use-outline-path= to ='title= will show title
+instead of the file name in refile targets. If the documen do not have
+a title, the filename will be used, similar to ='file= option.
+
 *** A new option for custom setting =org-agenda-show-outline-path= to show document title
 
 Setting =org-agenda-show-outline-path= to ='title= will show title
diff --git a/lisp/org-refile.el b/lisp/org-refile.el
index 16cff25bd..64f4ef7da 100644
--- a/lisp/org-refile.el
+++ b/lisp/org-refile.el
@@ -160,7 +160,8 @@ When `buffer-name', use the buffer name."
 	  (const :tag "Yes" t)
 	  (const :tag "Start with file name" file)
 	  (const :tag "Start with full file path" full-file-path)
-	  (const :tag "Start with buffer name" buffer-name)))
+	  (const :tag "Start with buffer name" buffer-name)
+	  (const :tag "Start with document title" title)))
 
 (defcustom org-outline-path-complete-in-steps t
   "Non-nil means complete the outline path in hierarchical steps.
@@ -319,6 +320,11 @@ converted to a headline before refiling."
 		 (push (list (and (buffer-file-name (buffer-base-buffer))
   (file-truename (buffer-file-name (buffer-base-buffer
  f nil nil) tgs))
+   (when (eq org-refile-use-outline-path 'title)
+ (push (list (or (org-get-title)
+ (and f (file-name-nondirectory f)))
+ f nil nil)
+   tgs))
 	   (org-with-wide-buffer
 		(goto-char (point-min))
 		(setq org-outline-path-cache nil)
@@ -345,7 +351,12 @@ converted to a headline before refiling."
(and (buffer-file-name (buffer-base-buffer))
 (file-name-nondirectory
  (buffer-file-name (buffer-base-buffer))
-   (`full-file-path
+   (`title (list
+(or (org-get-title)
+(and (buffer-file-name (buffer-base-buffer))
+ (file-name-nondirectory
+  (buffer-file-name (buffer-base-buffer)))
+   (`full-file-path
 (list (buffer-file-name
 	   (buffer-base-buffer
    (`buffer-name
@@ -633,7 +644,7 @@ this function appends the default value from
 	 (tbl (mapcar
 	   (lambda (x)
 		 (if (and (not (member org-refile-use-outline-path
-   '(file full-file-path)))
+   '(file full-file-path title)))
 			  (not (equal filename (nth 1 x
 		 (cons (concat (car x) extra " ("
    (file-name-nondirectory (nth 1 x)) ")")
diff --git 

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

[tomas]

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 malicious file from 
> setting an "yes, execute me automatically" variable?

While loading the file, only "safe variables" are set without
warning (actually it's a bit more complex: specific variable-
value pairs can be marked as "safe".

See e.g. "12.12 File Local Variables" in the elisp manual.

Cheers
-- 
t


signature.asc
Description: PGP signature

Org mode "style sheet" for software documentation

[Perry Smith]

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 ability to effectively create what I’ll call 
“macros”.  I’d like to be able to separate out things like file paths, code 
samples (both in line and block), keywords, environment variables, code 
variables, etc.  So, as I write, I would do (as a total pretend example) 
[var]foo_dog[var] to denote foo_dog as a code variable.  I’m wondering if that 
isn’t what the “BORDER” character is.  From the way the section is written, I 
would assume the leading border character must be the same as the trailing 
border character so I could do ~vfoo_docv~  where the “v” would be the border 
character?

OR… perhaps what this is trying to tell me is the first character after the 
leading marker and the last character before the trailing marker must not be 
whitespace characters since that is how it appears from all of the examples.

My logic is if I take the time to separate out all of the elements as I write 
the document, then I can later decide to format, for example, code snippets the 
same as variables.  It would also help me to be more consistent while I write 
because I’m (currently) having to remember “Ok… how did I format variables?  
Was that ‘code' or ‘italics'? … Hmm…”

If I’ve misunderstood this page, then perhaps to save a follow up email, can 
someone tell me if I can create “macros” within Org mode to do what I mentioned 
OR tell me that I really don’t want to go down that path for some reason.

Thank you for your help,
Perry



signature.asc
Description: Message signed with OpenPGP

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

[Max Nikulin]

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 the problem.

Maybe I break some use case, but I am unaware when namely downcased link
must be used.


I tracked this dlink business down to
75563bf71e6df356a5ae77a93152fcf913378107.
The relevant ML discussion is in
https://orgmode.org/list/4b51d104.9090...@jboecker.de


It is the thread I mentioned in the commit message.


So, it is probably safe to drop it, especially if tests are passing.


There is no tests for `org-open-file'. Checking of file existence, 
running an asynchronous process make it harder to create such tests.



;; First, try matching against apps-dlink if we
;; get a match here, store the match data for
;; later.
-   (let ((match (assoc-default dlink apps-dlink
-   'string-match)))
+   (let* ((case-fold-search t)
+   (match (assoc-default link apps-dlink
+ 'string-match)))


With this patch, `apps-dlink' name becomes completely confusing.
Is there any way to get rid of it as well? (or maybe rename to something
more reasonable).


Evey attempt to read this function gives a new surprise. I agree that 
dlink has no sense any more, see the new patches.From 283b2721857350e9eba4b8056b433764bf121222 Mon Sep 17 00:00:00 2001
From: Max Nikulin 
Date: Thu, 8 Sep 2022 19:02:37 +0700
Subject: [PATCH v2 1/3] org.el: Pass link match data to `org-file-apps'
 functions

* lisp/org.el (org--file-apps-entry-dlink-p): Fix it to pass match data
to handler functions from `org-open-file' alist when pattern field of
`org-file-apps' contains regexp subgroups.

Update `org--file-apps-entry-dlink-p' to use current convention for action
field of `org-file-apps' structure.  Currently it may be a function while
earlier s-expression was allowed.  Obsolete test wrongly separated actions
able to handle regexp subgroups matched in the link.  An example when
match data were not passed to the handler function:

(add-to-list
 'org-file-apps
 '("\\.pdf\\(?:\\.gz\\|\\.bz2\\|\\.xz\\)?\\(?:::.*\\)?\\'"
. my-open-pdf-locator))

Notice that lambda functions passed `consp' test, so namely
`defun' is required to reproduce the issue.

This change was missed in the commit:

 c8a3ab1e4 2016-02-03 18:30:17 +0100
 Nicolas Goaziou: `org-file-apps' accept functions instead of sexp

For discussion of the issue with evaluation of arbitrary expression see
https://list.orgmode.org/CALn3zoh+ACSU09eRurfwKjmCnw7i-_0KX7tA2jWqtu=vvqe...@mail.gmail.com/T/#u
Michael Brand. org-player and switch to lexical binding in org.el.
Sun, 17 Jan 2016 19:58:38 +0100
---
 lisp/org.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index 34560c83f..3d2fbd2cb 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8002,7 +8002,7 @@ a parameter."
 	  (> (regexp-opt-depth selector) 0)
 	  (or (and (stringp action)
 		   (string-match "%[0-9]" action))
-	  (consp action
+	  (functionp action
 (_ nil)))
 
 (defun org--file-apps-regexp-alist (list  add-auto-mode)
-- 
2.25.1

From 6800981712855f76c88703b0ca9905ec0af557cd Mon Sep 17 00:00:00 2001
From: Max Nikulin 
Date: Mon, 5 Sep 2022 13:54:25 +0700
Subject: [PATCH v2 2/3] org.el: Preserve case for link subgroups from
 `org-file-apps'

* lisp/org.el (org-open-file): Avoid matching of `org-file-apps' records
against the link converted to downcase since it caused incorrect
substitutions to the command.

Consider the following entry

(add-to-list
 'org-file-apps
 '("\\.PDF\\(?:\\.[gx]z\\|\\.bz2\\)?::\\(#[^:]*\\)::\\(.+\\)\\'"
  . "okular --find %2 -- %s%1"))

and the link

Without the patch

okular --find before -- /usr/share/doc/bash/bashref.pdf\#redirections

command is executed and the application can not resolve internal
cross-reference anchor.

In https://list.orgmode.org/4b51d104.9090...@jboecker.de/T/#u
https://list.orgmode.org/k2jfb2eb6811004041733zf176e0aq8367924746db8...@mail.gmail.com/T/#u
the purpose of `dlink' is not clarified, so I assume that the only
purpose is to allow matching file suffixes, e.g. ".pdf" vs ".PDF".
---
 lisp/org.el | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lisp/org.el b/lisp/org.el
index 3d2fbd2cb..236969649 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8134,7 +8134,6 @@ If the file does not exist, throw an error."
 	 (link (cond (line (concat file "::" (number-to-string line)))
 		 (search (concat file "::" search))
 		 (t file)))
-	 (dlink (downcase link))
 	 (ext
 	  (and (string-match "\\`.*?\\.\\([a-zA-Z0-9]+\\(\\.gz\\)?\\)\\'" dfile)
 	   

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

[Fedja Beader]

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?

Anyway, the point of my email was to suggest a change to org-mode such that it 
provides a pleasant out-of-the-box user experience for people like me. I want 
to use org-mode as a python/octave/R/whatever interactive notebook without 
having to spend several days learning elisp and the internal workings of Emacs. 
I have spent these days, days that could be better (sorry!) used working on 
actual projects of mine. But I spent this time and the time to articulate what 
I want and to write these emails in the hope that I will be the last person 
having to do so. I would also like to suggest org-mode to other people instead 
of Jupyter notebook without having to add "oh, btw, you might want to add these 
three pages of alien code to your init.el to make it usable".

To go a bit further off-thread, this change might seem unnecessary. However, 
the other changes I want is also auto-executing all modified code blocks on 
file save and/or when the cursor moves out of it, auto-executing dependent 
blocks when their dependency changes (e.g. blocks full of constants) or marking 
blocks as stale. But I will make suggestions to improve these things in later 
emails, once I know what I want.

Hello Greg,

Agreed, just yesterday I must have pressed C-c C-c "yes" three times a minute 
evaluating an embedded Octave script. The current default configuration is not 
pleasant at all.

Hello Ihor,

> Then, what about the following:
> 1. Set org-confirm-babel-evaluate globally to t
> 2. In the files you maintain, you can always put
>file-local/directory-local value of org-confirm-babel-evaluate to
>nil.
> 3. We can modify org-babel-confirm-evaluate _function_ to accept four
>possible answers: yes, no, yes for all in buffer, no for all in
>buffer. The extra 2 options will set buffer-local value of
>org-confirm-babel-evaluate in the current Emacs session

Don't know about option (1), (2) seems insecure at first glance, for the 
reasons mentioned above. (3) sounds good (yes/no/always/never?) and what I want.

Re: Problem with installation

[Ihor Radchenko]

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: Problem with installation

[Ihor Radchenko]

[ 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.tar.gz  of Org-mode –
> these archives are updated every day at midnight.
> -
>
> However those links are not working.

You are right. I just updated the link in
https://git.sr.ht/~bzg/worg/commit/bf2d9967abf582b5dd34dfaca830988c0a308c87

The change should land onto the website soon.

Best,
Ihor

Re: Problem with installation

[Ihor Radchenko]

[ 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

[Ihor Radchenko]

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 "Cannot open load file" "No
> such file or directo
> ry" "org-version")

Thanks for reporting!
However, I am unable to reproduce the issue on my side.
Could you please check what is your Emacs version?

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

Problem with installation

[anilomjf]

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 template.   =
= Setting "oldorg" as the default target.=
= Please adapt local.mk to your local setup! =
==
Loading /home/javi/org-mode/lisp/org-compat.el (source)...
Eager macro-expansion failure: (file-missing "Cannot open load file" "No
such file or directo
ry" "org-version")
Eager macro-expansion failure: (file-missing "Cannot open load file" "No
such file or directo
ry" "org-version")
Cannot open load file: No such file or directory, org-version
make: [mk/targets.mk:91: local.mk] Error 255 (ignored)
make -C lisp autoloads
make[1]: Entering directory '/home/javi/org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
org-install.elc
org-version: 9.5.5 (release_9.5.5-768-geb5ef0)
Loading /home/javi/org-mode/lisp/org-compat.el (source)...
Eager macro-expansion failure: (file-missing "Cannot open load file" "No
such file or directo
ry" "org-version")
Eager macro-expansion failure: (file-missing "Cannot open load file" "No
such file or directo
ry" "org-version")
Cannot open load file: No such file or directory, org-version
make[1]: *** [Makefile:72: org-version.el] Error 255
make[1]: Leaving directory '/home/javi/org-mode/lisp'
make: *** [mk/targets.mk:133: autoloads] Error 2

It seems like the file org-version is missing.

Thank you.

Re: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]

[Ihor Radchenko]

Andrés Ramírez  writes:

> org-agenda-list generation time takes too much time compared with the
> same setup with emacs27.
>
> This is org-agenda-list output from 28. (takes aproximately 4m21s)
> ...
> This is org-agenda-list output from 27. (takes 15s)
>
> Emacs  : GNU Emacs 28.1 (build 1, armv7l-unknown-linux-gnueabihf)
>  of 2022-05-27
> Package: Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @ 
> /usr/share/emacs/28.1/lisp/org/)

The slowdown is possible as a side-effect of some bugfixes.
However, the newest development version of Org should not have these
performance issues.

Can you try with the latest Org version
(https://elpa.gnu.org/devel/org.html)? You will need to add
https://elpa.gnu.org/devel/ to your package archives.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92