Bug: org-capture does not work if called from minibuffer (Org mode version 9.6.10 (9.6.10-n/a-g902975)

[Cletip Cletip]

Hello,

It's almost the same as described here:
https://mail.gnu.org/archive/html/emacs-orgmode/2020-12/msg00199.html. BUT,
this only comes into play in the following case:

Suppose you want to complete an org-capture template with this: “%^{Title}”.
When you call this capture, the minibuffer allows you to select the title
(in the minibuffer). But, if you want to capture "from" this minibuffer, it
crashes org-capture with the error (just after the choice of the second
template) :
org-capture: Capture template 'u': Can't expand minibuffer to full frame.

Concrete use case: capturing an org-roam node (and complete the title),
trying to insert a node that doesn't yet exist (and therefore reopening
org-capture) in the title of the first capture process.

Thank you in advance for your reply.

Inactive timestamp with TODO are exported in .ics file

[Cletip Cletip]

Hello to all,

I hope this message finds you well. I am writing to seek assistance with an
issue I am facing regarding the org-icalendar export and agenda visibility
in Emacs.

Despite setting (org-icalendar-with-timestamps 'active), I am facing an
issue where the export includes items with the TODO state and inactive
timestamp. Below are four examples illustrating this problem, with the code
that I am using to try the export (copy and paste the code and the four
events (in a file "Test.org" in /tmp/ for example), and execute the code to
see that the "Tickler" is exported, despite it is an inactive timestamp) :

#+begin_src emacs-lisp

  (let ((org-agenda-files `(,(buffer-file-name)))
(org-icalendar-combined-agenda-file "/tmp/agenda.ics")

(org-icalendar-with-timestamps 'active)
(org-icalendar-include-todo nil) ;; nil to not clone scheduled TODO task
(org-icalendar-use-scheduled'(event-if-todo-not-done event-if-not-todo))
(org-icalendar-use-deadline '(event-if-not-todo event-if-todo-not-done))
)
;; here is the export
(org-icalendar-combine-agenda-files)
)

#+end_src

 A simple appointment (exported)
:PROPERTIES:
:ID:   31ea3244-769b-4ead-80d5-1573f377de86
:END:

<2023-08-02 13:00-14:00>

 TODO A tickler (TODO + scheduled + inactive timestamp) (not exported)
SCHEDULED:[2023-08-05 Sat 18:33]
:PROPERTIES:
:ID:   71fc9702-f479-4d36-ad6f-457892df6ab9
:END:

 TODO A task that needs to be done and scheduled (exported)
SCHEDULED: <2023-08-03 Thu 13:00>
:PROPERTIES:
:ID:   3bccc447-85bb-4ef0-89f7-8ed6c6ff8891
:END:

 TODO A task with a deadline (exported, two times)
SCHEDULED: <2023-08-01 Tue 13:00> DEADLINE: <2023-08-10 Thu 13:00>
:PROPERTIES:
:ID:   2d96d62e-5420-4443-be8d-a9456ea9551f
:END:

Why are the "tickler" exported, despite it is an inactive timestamp ?
Is the a solution to export appointment and the tasks, exclude the tickler ?

I appreciate any insights or suggestions the community can provide to help
me address these issue ^^

Thank you for your time and assistance.

Re: [BUG] Tangle with symbolic links don't work

[Cletip Cletip]

Hello !

Sorry to bring up the subject again, but I didn't quite understand what the
solution was: should I modify the function ? Is it modified in a new
version of org-mode ?

Thank you in advance for your response.

Le mar. 7 nov. 2023 à 12:28, Ihor Radchenko  a écrit :

> Max Nikulin  writes:
>
> >> Max, do you see any pitfalls using `file-truename'?
> >
> > Sorry, I am not familiar with related code path. That is why I can not
> > reason what way to deal with file name is safer.
> >
> > If there is a world-writable directory in the file path (usually
> > $TMPDIR) then `file-truename' is less safe, see
> >
> https://www.kernel.org/doc/html/latest/admin-guide/sysctl/fs.html#protected-symlinks
>
> Thanks!
>
> > In general, I am never sure that Org code follows best practices in
> > respect to security in general and in respect to /tmp in particular. The
> > following citation is unrelated to /tmp, but the same proposed patch has
> > an issue with predictable name in /tmp:
>
> We have to compromise between usability and safety... but probably not
> in this case.
>
> > Even when /tmp or similar directories are not involved, a proper
> > strategy to replace file content should be carefully chosen. E.g. cp(1)
> > preserves inode number while install(1) replaces target file atomically
> > (create a temporary one and rename). The latter way is more suitable for
> > shared libraries since it allows running application to continue call
> > function from the deleted file.
>
> What we actually use is Elisp API. For export and tangling, we use
> `write-region' - it correctly handles TRAMP files with lower-level
> details taken care of.
>
> I can now see that blindly expanding to `file-truename' may not be wise.
>
> Without `file-truename', the difference between ox.el (that works for
> Cletip) and ob-tangle.el is that ob-tangle explicitly deletes the tangle
> target before tangling:
>
> `org-babel-tangle':
>
>  ;; erase previous file
>  (when (file-exists-p file-name)
>(delete-file file-name))
>  (write-region nil nil file-name)
>  (mapc (lambda (mode) (set-file-modes file-name mode))
> modes)
>
> Rather than using `file-truename', we may instead remove the
> `delete-file' part. This way, we will not risk changing file modes in
> the original files and always modify the symlink, if the tangle target
> is an existing symlink.
>
> > I know, it is not an answer you expected from me, but giving a better
> > one require to much efforts to read the code and to debug it.
>
> It is exactly an answer I expected, actually :)
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>

[BUG] Tangle with symbolic links don't work

[Cletip Cletip]

Hello everyone,

I'm reaching out to discuss a challenge I've encountered while working with
Org-mode, specifically during the tangling process of code blocks.

The Issue:
I have an Org file, test.org, from which I tangle code blocks into test.py.
The complication arises because test.py is a symbolic link. Each time I
perform the tangling operation, the symbolic link is unfortunately
overwritten.

Interestingly, when exporting documents to formats such as .tex, .html, or
others, Org-mode respects the symbolic link, which is the desired behavior.
However, this is not the case with tangling, which is quite perplexing.

My Org mode version : 9.6.10 (9.6.10-n/a-g902975...)

Proposed Solution:
I've identified a potential fix that involves a minor adjustment in the
ob-tangle.el file:

Original line (259):

(let ((file-name (car by-fn)))

Modified line:

(let ((file-name (file-truename (car by-fn

While this solution appears effective at first glance, I haven't
extensively tested all edge cases. I would greatly appreciate your insights
on whether this is a robust solution ^^.

Thanks in advance for your answer.

Re: Add new word before an org-agenda entry (like "MODIFIED")

[Cletip Cletip]

I know how to create a custom agenda block, but how insert this ? Can I
just have some leads ?

Le jeu. 12 oct. 2023 à 13:39, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > Here's an example for clarification:
> > Consider this line in org-agenda:
> >
> > 14:08-14:10 Clocked: (0:02) name-of-the-heading
> >
> > I want exactly the same thing, but not with the "Clocked" word !
>
> This is not easy. The supported log types are hard-coded in
> `org-agenda-get-progress'.
>
> You may need to implement a custom agenda block type to achieve what you
> want.
>
> --
> Ihor Radchenko // yantar92,
> 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: [BUG] Inactive interval is not correctly displayed in agenda view (was: [BUG?] Org-agenda doesn't work with this error : Search failed: "\]+\)>")

[Cletip Cletip]

Very cool, thanks !

Le mer. 11 oct. 2023 à 11:03, Ihor Radchenko  a écrit :

> Ihor Radchenko  writes:
>
> >> if I have the following heading :
> >>
> >> * A test
> >>  [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
> >>  <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>
> >>
> >> The "org interval" are not respected for the inactive timestamp. See
> what
> >> is the result in org-agenda :
> >>
> >>  17:25-17:30   A test
> >>  17:25-17:25  [ A test
> >>  17:30-17:30  [ A test
> >>
> >> The first line is what I want : a beginning hour, with a end. But, the
> two
> >> other are not normal : it must be the same line.
> >
> > I can reproduce. Indeed looks odd.
> > I will look closer at this problem later.
>
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e1569918c
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>

Re: [BUG] Inactive interval is not correctly displayed in agenda view (was: [BUG?] Org-agenda doesn't work with this error : Search failed: "\]+\)>")

[Cletip Cletip]

>
> I will look closer at this problem later.
> No need. I changed the subject to branch off this bug report as a new
> thread.

Thanks a lot :) have a nice day !

Le mar. 10 oct. 2023 à 18:31, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > Now that I have the diary in front of me, I get the impression that
> there's
> > another problem, and I guess it's not as simple as a simple regular
> > expression.
> >
> > if I have the following heading :
> >
> > * A test
> >  [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
> >  <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>
> >
> > The "org interval" are not respected for the inactive timestamp. See what
> > is the result in org-agenda :
> >
> >  17:25-17:30   A test
> >  17:25-17:25  [ A test
> >  17:30-17:30  [ A test
> >
> > The first line is what I want : a beginning hour, with a end. But, the
> two
> > other are not normal : it must be the same line.
>
> I can reproduce. Indeed looks odd.
> I will look closer at this problem later.
>
> > Must I send another mail not in this conversation ?
>
> No need. I changed the subject to branch off this bug report as a new
> thread.
>
> --
> Ihor Radchenko // yantar92,
> 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: [BUG?] Org-agenda doesn't work with this error : Search failed: "\]+\)>"

[Cletip Cletip]

>
> See https://list.orgmode.org/orgmode/87edkhnbn4@shell.onfire.org/

Perfect, that solve the problem ! Incredible reactivity, thanks !

I now also backported the fix onto bugfix branch.

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=558db89e4

I don't really understand what mean that : what should I do to have this ?
Update org-mode ? Another things ?

Thanks you for your help ^^

Now that I have the diary in front of me, I get the impression that there's
another problem, and I guess it's not as simple as a simple regular
expression.

if I have the following heading :

* A test
 [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
 <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>

The "org interval" are not respected for the inactive timestamp. See what
is the result in org-agenda :

 17:25-17:30   A test
 17:25-17:25  [ A test
 17:30-17:30  [ A test

The first line is what I want : a beginning hour, with a end. But, the two
other are not normal : it must be the same line.
Must I send another mail not in this conversation ?

Thanks you again for your futur answer

Le mar. 10 oct. 2023 à 17:47, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > I just encountered a strange bug (maybe) in org-mode, starting from
> version
> > 9.6. I don't quite understand why, but it happens when I display the
> agenda
> > (to be precise: M-x org-agenda a).
> >
> > This only happens (from the causes I found) when there is: SCHEDULED with
> > inactive timestamp without a parent heading. This triggers the following
> > error for me:
> >
> > Search failed: "\]+\)>"
>
> See https://list.orgmode.org/orgmode/87edkhnbn4@shell.onfire.org/
> I now also backported the fix onto bugfix branch.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=558db89e4
>
> --
> Ihor Radchenko // yantar92,
> 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>
>

[BUG?] Org-agenda doesn't work with this error : Search failed: "\]+\)>"

[Cletip Cletip]

Hello!

I just encountered a strange bug (maybe) in org-mode, starting from version
9.6. I don't quite understand why, but it happens when I display the agenda
(to be precise: M-x org-agenda a).

This only happens (from the causes I found) when there is: SCHEDULED with
inactive timestamp without a parent heading. This triggers the following
error for me:

Search failed: "\]+\)>"

My version of emacs : GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+
Version 3.24.20, cairo version 1.16.0) of 2022-05-31

Where it doesn't bug:
Org mode version 9.5.5 (9.5.5-n/a-g8ef620)
And older versions.

Where it bugs:
Org mode version 9.6 (9.6-n/a-gb3da4)
And newer versions.

Configuration (I use elpaca to quickly install packages, I've included the
installation even though it may not be necessary):

#+begin_src emacs-lisp

  ;;installation d'elpaca
  ;; -
  (defvar elpaca-installer-version 0.4)
  (defvar elpaca-directory (expand-file-name "elpaca/"
user-emacs-directory))
  (defvar elpaca-builds-directory (expand-file-name "builds/"
elpaca-directory))
  (defvar elpaca-repos-directory (expand-file-name "repos/"
elpaca-directory))
  (defvar elpaca-order '(elpaca :repo "
https://github.com/progfolio/elpaca.git;
:ref nil
:files (:defaults (:exclude "extensions"))
:build (:not elpaca--activate-package)))
  (let* ((repo  (expand-file-name "elpaca/" elpaca-repos-directory))
(build (expand-file-name "elpaca/" elpaca-builds-directory))
(order (cdr elpaca-order))
(default-directory repo))
(add-to-list 'load-path (if (file-exists-p build) build repo))
(unless (file-exists-p repo)
  (make-directory repo t)
  (when (< emacs-major-version 28) (require 'subr-x))
  (condition-case-unless-debug err
 (if-let ((buffer (pop-to-buffer-same-window "*elpaca-bootstrap*"))
  ((zerop (call-process "git" nil buffer t "clone"
(plist-get order :repo) repo)))
  ((zerop (call-process "git" nil buffer t "checkout"
(or (plist-get order :ref) "--"
  (emacs (concat invocation-directory invocation-name))
  ((zerop (call-process emacs nil buffer nil "-Q" "-L" "." "--batch"
"--eval" "(byte-recompile-directory \".\" 0 'force)")))
  ((require 'elpaca))
  ((elpaca-generate-autoloads "elpaca" repo)))
 (kill-buffer buffer)
   (error "%s" (with-current-buffer buffer (buffer-string
((error) (warn "%s" err) (delete-directory repo 'recursive
(unless (require 'elpaca-autoloads nil t)
  (require 'elpaca)
  (elpaca-generate-autoloads "elpaca" repo)
  ;; (load "./elpaca-autoloads.el") ;; ne marche pas pour termux
  (load (expand-file-name "elpaca-autoloads.el" repo))
  ))

  (add-hook 'after-init-hook #'elpaca-process-queues)
  (elpaca `(,@elpaca-order))
  (elpaca-wait)
  ;; -

  (elpaca
;; or the version you like
  (org :type git :host github :repo "bzg/org-mode" :ref "b3da427")
(setq org-agenda-files '("/home/.../test.org"))
)

#+end_src

In test.org :

#+begin_example
* TODO Séance
SCHEDULED: [2023-10-10 Tue]
#+end_example

And... that's it!
I hope this is not too troublesome a bug to resolve ^^

Thank you for your response!

Add new word before an org-agenda entry (like "MODIFIED")

[Cletip Cletip]

Hello, everyone! I have a question that may be complex to answer. I
apologize in advance for my limited vocabulary; I will use an example to
elucidate my question better.

Objective: I wish to track when a heading is modified using org-agenda. To
achieve this, I automatically insert an inactive timestamp in the LOGBOOK
drawer whenever a note is modified. However, how can I display the item in
org-agenda with the prefix "MODIFIED:" or another indicator before the
heading to show that I made a modification ?

Here's an example for clarification:
Consider this line in org-agenda:

14:08-14:10 Clocked: (0:02) name-of-the-heading

I want exactly the same thing, but not with the "Clocked" word !

Another example : I would like this entry/heading/item :

** An example
:PROPERTIES:
:CREATED: [2023-09-29 Fri 23:07]
:END:
:LOGBOOK:
MODIFIED: [2023-10-01 Sun 14:09]--[2023-10-01 Sun 14:35]
CLOCK: [2023-09-30 Sat 23:19]--[2023-09-30 Sat 23:25] => 0:06
MODIFIED: [2023-09-30 Sat 14:08]--[2023-09-30 Sat 14:20]
:END:

with the word "MODIFIED:" precede the entry in the org-agenda.

Is this feasible? Can you suggest alternative methods?

Thanks in advance for your futur answer :)

Re: Link type in org-mode, but with org-roam ?

[Cletip Cletip]

>
> But I am very willing to help you install it and try it all out and
> make it workable on your computer, in one on one chat or by e-mail,
> that will work well.


Yes, I'd be very happy to try it. Contact me by email when you have time. I
am available on weekends. I would definitely prefer a call to be able to
exchange easily, via the application you want.

> The problem and the great weakness of such a system is that I have
> > to define the queryable information in advance.


> No, you need not think of that. Do you use database?

I am not thinking in advance about "queryable" information. I am
> thinking of structure, or types, and do not worry of future. All
> types, columns, anything is automatically capable to be queried.


I was talking about my system which was made with org-roam, so the
information stored in the notes is in plain text. But, to make them
queryable, I have to add "metadata" as said before with key-value.
So I'm using a database, but I don't want to bother thinking about how I
can add new information to my system. You, you need to think about "what
describes this information?" If it's someone, you create a new table (not
sure if this is this term to use) to hold that knowledge.
I don't want to think about that, I just want to put the information in and
find it without thinking about tables.

Because of the design of tables, and conditional correct entries into
> the database, it becomes very easy to find for example "POST BOX"
> address of all people in Mwanza city.


Here, everything is queryable, because you have already thought of all the
possible cases that could happen. In my system, I decided to do the
opposite: why think of a particular case if I'm not even sure I'm doing it?

But our goals are not the same, you have to have a solid system for several
people, I do something much more personal. So, it's ok.

> Whereas you may have the opposite problem: every piece of
> > information is queryable, but a new piece of information takes a
> > long time to put away.


> I do not understand "put away", is it to "remove it"? I do not
> understand the problem.


Sorry bad translation.
I wanted to say that adding a new type of information can be time
consuming: you have to add the table, and above all check that another
table does not already exist to do the same thing.
So you need excellent documentation, hoping that the system itself doesn't
become too "cluttered" for the user.

> You can't just put information down like that (maybe I am wrong,
> > maybe you can. But from what I understand, no). And that's the
> > dilemma: either you make something extremely rigid, but "queryable",
> > i.e. you can query the system itself with requests.

Making database based structure of objects is to many degrees way more
> beneficial than having it without structure.


For your purpose, yes. For mine, no. I think that every thing that has to
have a special presentation / type in the database is an exception: the
user has to think / look that, if he wants to add a contact, he has to look
for the type "contact".
I would like my system to detect by itself that when I give a node/heading
org-mode as title "A-name A-forname", it understands by itself that it is a
contact. And if I put a phone number underneath, I can just ask him "give
me the phone number of X", and he gives it to me correctly.

I repeat because I don't want to offend you: we don't have the same goals,
so it is normal that our methods are different.
On the other hand, I would very much like to test your method, it intrigues
and interests me a lot.


> > Or we do something extremely flexible, exactly like a big org-mode
> > file where we just put the information, and the user can use his
> > method (grep for example).

For single user that may be fine. For collaborative work, multi-user
> access is not, or sharing of information, it is not. That is why Org
> development strive to provide more and more structure, something I
> said, they try to make it like a database, but because there is no
> structure, it becomes the never ending story of milions of bugs.


I agree with you, although I don't know if the goal of the org-mode
developers is to do this.



> In my work I use meta level. First I am liberated from Org mode, or
> any kind of mode. And I like flexibility to mix various markups. I can
> use universal hyperlinks that convert themselves into necessary
> markup. I don't like being dependent on some "mode".


> If markup is Org, hyperlink will become Org hyperlink, if markup is
> Markdown, hyperlink will become Markdown link, if it is text, it will
> be shown in text. Why do I need to record 3 versions of same document,
> better one, which can be just represented in different way.


After that, it's the same for org-mode, it can export in a lot of formats,
so in the end you're just adding an extra layer of abstraction to export to
org-mode.

But I see the idea of not depending on org-mode anymore

Maybe you wish to say how 

Link type in org-mode, but with org-roam ?

[Cletip Cletip]

Hello everyone.

I apologize in advance for :
- my org-mode philosophy (my ideas may be totally stupid, meaningless, or
even contrary to the original org-mode philosophy)
- my knowledge of the mailing-list (my mail may be badly organised, badly
indented, the code unclear etc)
- any other point that might irritate you because of my lack of knowledge
of certain things
- the length of this mail
- for my bad bad bad english

 I'm going to get straight to the point and try to be as concise as
possible, just for context: I've been using org-mode every day for at least
2 years. I want to make it my personal knowledge/information manager. I
understand code relatively quickly, I understand less when it comes to
writing it. I've done a lot of research on note-taking methods... well, you
can see my profile I think.
So, my goal: to make a concise system with org-mode, org-roam, org-attach,
org-agenda etc... a "classic" goal for some of us :).
I won't describe any of the tools mentioned here, it would make the mail
much too long.

The problem: need to make "queryable" notes to do more or less complex
operations. For example, run the code of all headings/notes that have the
tag "ubuntu", to allow me to reinstall my computer for example. This
problem is trivial to solve with tags (a simple "dolist" is enough), but
tags will not always be enough... So you need to be able to store
"value-key" data, in order to make "select me all the people with a phone
number starting with 06" queries. This works perfectly well with this:
https://github.com/d12frosted/vulpea#metadata.


This gives things of the following conceptual form:
note1(where the metadata is stored) -> relationship -> note2/OrValue.

What is stored in the database must be only the IDs (not the titles of the
note for example), but the description is there for the user. This allows
not to have a controlled vocabulary: when searching, we look for a note id,
and not a string. On the other hand, what is displayed to the user in the
notes is the description, which is very practical.

note1 is therefore the id of a note (in the org-roam sense).
Relation is the id of the "metadata"/type of the desired relation.
And note2/Value is the value of the relationship, which may be an id of
another note or just a value.
In practice, it is therefore in this form:
- [[id:20230112135328669948][Name you want, but respect the idea of the
concept behind the id]] :: [[id:20220617105453042719][Another note]]
- [[id:20230112135328669948][a metadata only with a value]] :: just a value

The concept is close to the "In-Buffer Settings", with a "#+": it's a
key-value. Except that In-Buffer Settings, org-mode can't understand that
there is a link or something else, org-mode understands just a string,
which will be parsed to modify org-mode's behaviour on that file, or for a
export, etc.

Concrete example: if I want to store all my music (eache music = a note
with an attached file), I have two choices:
- I put the tag "music", in the org-roam sense (i.e. "#+filetag: #music")
for each note.
- But, this amounts to writing: aMusic relation(here, "tagged with" for
example) note2 or in practice: - [[idOfTaggedwith][tag]]:
[[idOfTheConceptOfMusic][music]]. So we can make the following request:
give me the notes with the metadata "idOfTaggedwith" with the value
"idOfTheConceptOfMusic" (because, I remind you, only ids are stored. Just
make a convenient interface for the user, and he won't even need to think
about ids).

Conceptually and omitting the other usefulness of In-Buffer Settings, it's
exactly the same thing.

Furthermore, I think this problem is part of a more global problem: they
are "typed links". They can be called by many names: link tags
https://org-roam.discourse.group/t/add-link-tags-feature/171, link types,
relational links, etc. If someone has the "right" name to describe this...

And therein lies my real problem: I haven't found a single good solution to
achieve this. This problem is mostly related to org-roam, but org-roam is
based on org-mode, that's why I'm writing here.
I thought of the following solution, so I'd like to have some opinions.
Main idea: make a link type that would be recognized not by "X:path" with X
= link type, but by a regular expression, where if X respects a certain
format, it is recognized as a relationship.

As you know, external links can be of the form "X:path", where X equals id,
file, gnus etc. Note: Org-roam stores all types of links.
So we can make the following type of links:
[[A:B][description]]
where
- A is the id of a note known by org-roam
- B is the id of a note, or string, or numeric value, etc
- description is a description (what a precision)

This allows org-roam to store the type of the relationship, A, and the
value of the relationship, B. So we can make queries like: "all notes where
idOfTaggedwith = idOfTheConceptOfMusic".

Implementation (functional on my side. It took me a lot of time, because I
didn't know the org-mode code. But it's 

Re: How to center an image directly in org-mode (without exporting)

[Cletip Cletip]

Thanks you for your answer,
thanks for the tips, I will see that in detail.

Le ven. 4 nov. 2022 à 05:53, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > My problem is quite simple to understand: when I activate
> > "org-toggle-inline-images", I would like my images to be centered.
> Indeed,
> > I tried this in a org-file
> >
> > #+ATTR_ORG: :width 800 :center t
> >
> > [[file:images/anImage.png]]
> >
> >
> > But it obviously doesn't work.
>
> AFAIK, there is no easy way to do this, especially if you want the
> centering to be preserved on resize.
>
> > Does anyone have a tip?
> >
> > (I'm thinking of creating a function that, each time the size of the
> window
> > changes, readjusts the number of spaces to put so that my image is
> > centered. It's not a very clean solution, but could it work?)
>
> What you are thinking is probably the only sane way. Though you do not
> have to insert actual spaces. May instead use display property. See
> 40.16.3 Pixel Specification for Spaces section of Elisp manual.
>
> --
> Ihor Radchenko // yantar92,
> 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>
>

How to center an image directly in org-mode (without exporting)

[Cletip Cletip]

Hello to all,

My problem is quite simple to understand: when I activate
"org-toggle-inline-images", I would like my images to be centered. Indeed,
I tried this in a org-file

#+ATTR_ORG: :width 800 :center t

[[file:images/anImage.png]]


But it obviously doesn't work.

Does anyone have a tip?

(I'm thinking of creating a function that, each time the size of the window
changes, readjusts the number of spaces to put so that my image is
centered. It's not a very clean solution, but could it work?)

Thanks in advance

Re: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Ok thanks a lot for your answers, I made the function, if ever it can
interest someone one day


(defun org-get-tags-with-hierarchy-at-point()
  "Return the list of tag WITH the sub-tags if they exist at point"
  (interactive)
  (let ((tags-heading (org-get-tags))
(tags-result '()))
(dolist (tag tags-heading)
  (dolist (tag-to-add (org-tags-expand tag t))
(push tag-to-add tags-result)
)
  )
(delete-dups tags-result)
)
  )

Do not hesitate to change the "tags-heading" variable to select a different
heading

Thanks again for your answers !

Le jeu. 1 sept. 2022 à 09:03, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > Just one last clarification to be sure: there is no native function in
> > org-mode to have the list of tags with a hierarchy? I have to write my
> > function with the two functions
> > org-get-tags and org-tags-expand
> > to get the result I want : a list of tags that takes into account the
> > hierarchy defined by the "org-tag-alist" variable
>
> AFAIK, we have no such function.
>
> --
> 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: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Just one last clarification to be sure: there is no native function in
org-mode to have the list of tags with a hierarchy? I have to write my
function with the two functions
org-get-tags and org-tags-expand
to get the result I want : a list of tags that takes into account the
hierarchy defined by the "org-tag-alist" variable

Le mer. 31 août 2022 à 13:25, Cletip Cletip  a
écrit :

> Sorry, I found the solution : i must just give one argument non-nil to the
> function "org-tags-expand".
> Like this :
> (org-tags-expand "GTD" t)
>
> It's perfect, thanks a lot for your help !
>
> Le mer. 31 août 2022 à 11:01, Cletip Cletip  a
> écrit :
>
>> Thank you for your answer, and sorry for the late reply
>>
>> Ok I think I understood the mechanism, but I don't understand how to use
>> this regular expression (the one given by, for example,
>> (org-tags-expand "GTD")
>> which gives me the regular expression "with the other tags"
>> )
>>
>> I see perfectly the idea : a search is done with org-agenda with this
>> regular expression. But I can't use it.
>>
>> The problem is that I don't know how to use this regular expression with
>> a function that returns the tags. Do you have any clue (piece of code where
>> it is already used ? A function allowing me to translate this regular
>> expression into a simple tag? Do I just have to convert this regular
>> expression into a list of tags? Is it possible? I'm asking myself all these
>> questions because I just don't know where to go ^^)
>>
>> Thanks in advance for your future answer.
>>
>>
>> Le lun. 29 août 2022 à 13:57, Ihor Radchenko  a
>> écrit :
>>
>>> Cletip Cletip  writes:
>>>
>>> > Yes I understand both perfectly. I think some people (like me) would
>>> like
>>> > to connect them, others would not want to bring them together.
>>> > But how to get the hierarchy (or the families) used by org agenda with
>>> a
>>> > function like "org-get-tags" ?
>>>
>>> You will probably need to combine org-get-tags output with regexp
>>> generated by org-tags-expand. Tag hierarchy in Org is a just a search
>>> wrapper - no real tags are changed in the file; only the matching.
>>>
>>> --
>>> 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: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Sorry, I found the solution : i must just give one argument non-nil to the
function "org-tags-expand".
Like this :
(org-tags-expand "GTD" t)

It's perfect, thanks a lot for your help !

Le mer. 31 août 2022 à 11:01, Cletip Cletip  a
écrit :

> Thank you for your answer, and sorry for the late reply
>
> Ok I think I understood the mechanism, but I don't understand how to use
> this regular expression (the one given by, for example,
> (org-tags-expand "GTD")
> which gives me the regular expression "with the other tags"
> )
>
> I see perfectly the idea : a search is done with org-agenda with this
> regular expression. But I can't use it.
>
> The problem is that I don't know how to use this regular expression with a
> function that returns the tags. Do you have any clue (piece of code where
> it is already used ? A function allowing me to translate this regular
> expression into a simple tag? Do I just have to convert this regular
> expression into a list of tags? Is it possible? I'm asking myself all these
> questions because I just don't know where to go ^^)
>
> Thanks in advance for your future answer.
>
>
> Le lun. 29 août 2022 à 13:57, Ihor Radchenko  a
> écrit :
>
>> Cletip Cletip  writes:
>>
>> > Yes I understand both perfectly. I think some people (like me) would
>> like
>> > to connect them, others would not want to bring them together.
>> > But how to get the hierarchy (or the families) used by org agenda with a
>> > function like "org-get-tags" ?
>>
>> You will probably need to combine org-get-tags output with regexp
>> generated by org-tags-expand. Tag hierarchy in Org is a just a search
>> wrapper - no real tags are changed in the file; only the matching.
>>
>> --
>> 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: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Thank you for your answer, and sorry for the late reply

Ok I think I understood the mechanism, but I don't understand how to use
this regular expression (the one given by, for example,
(org-tags-expand "GTD")
which gives me the regular expression "with the other tags"
)

I see perfectly the idea : a search is done with org-agenda with this
regular expression. But I can't use it.

The problem is that I don't know how to use this regular expression with a
function that returns the tags. Do you have any clue (piece of code where
it is already used ? A function allowing me to translate this regular
expression into a simple tag? Do I just have to convert this regular
expression into a list of tags? Is it possible? I'm asking myself all these
questions because I just don't know where to go ^^)

Thanks in advance for your future answer.


Le lun. 29 août 2022 à 13:57, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > Yes I understand both perfectly. I think some people (like me) would like
> > to connect them, others would not want to bring them together.
> > But how to get the hierarchy (or the families) used by org agenda with a
> > function like "org-get-tags" ?
>
> You will probably need to combine org-get-tags output with regexp
> generated by org-tags-expand. Tag hierarchy in Org is a just a search
> wrapper - no real tags are changed in the file; only the matching.
>
> --
> 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: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Thanks you for your answer,

Yes I understand both perfectly. I think some people (like me) would like
to connect them, others would not want to bring them together.
But how to get the hierarchy (or the families) used by org agenda with a
function like "org-get-tags" ?

PS: sorry for the bad vocabulary, I followed the same name as the wiki, I
should have been more careful and given more details. Is my question clear
enough?


Le dim. 28 août 2022 à 21:15, Daniel Fleischer  a
écrit :

> Cletip Cletip [2022-08-28 Sun 18:34] wrote:
>
> > I may not have been specific enough:
> > I want the tags also inherited with this "method"
> https://orgmode.org/manual/Tag-Hierarchy.html.
>
> I think these are 2 mechanisms that only share the name "hierarchy". One
> is headline hierarchy: a headline shares the tags of its ancestors. It's
> local information, it's about the categories this headline are part of
> because of its location in the document.
>
> The other mechanism is for grouping tags into families and is used in
> the agenda; each family has a representative and you can search for it
> instead of searching all the individual members.
>
> I think it makes sense, but you might want these to be related.
>
> --
>
> Daniel Fleischer
>

Re: Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Thank you for your answer!

I may not have been specific enough:
I want the tags also inherited with this "method"
https://orgmode.org/manual/Tag-Hierarchy.html.


So imagine this in your configuration file

(setq org-tag-alist '((:startgrouptag)
  ("GTD")
  (:grouptags)
  ("Control")
  (:Persp)
  (:endgrouptag)
  (:startgrouptag)
  ( Control)
  (:grouptags)
  ("Context")
  (:Task")
  (:endgrouptag))


So, if I put the "Control" tag, I am also supposed to have the "GTD" tag,
because "Control" is a child of "GTD".

But, with the "org-get-tags" function, I don't have this famous "GTD" tag

Le dim. 28 août 2022 à 18:22, Juan Manuel Macías  a
écrit :

> Cletip Cletip writes:
>
> > After multiple searches on the internet, I did not find the answer to
> > my question (which is the subject of this mail): when calling the
> > "org-get-tags" function, only the tags put on the heading, and not the
> > inherited tags, are retrieved. How can I get the inherited tags as
> > well? Does such a function already exist? Did I miss an essential
> > variable?
>
> In my case, I do manage to get the iherited tags. Do you have
> `org-use-tag-inheritance' set to non-nil?
>
> According to the `org-get-tags' docstring:
>
> > According to ‘org-use-tag-inheritance’, tags may be inherited from
> > parent headlines, and from the whole document, through
> > ‘org-file-tags’. In this case, the returned list of tags contains tags
> > in this order: file tags, tags inherited from parent headlines, local
> > tags. If a tag appears multiple times, only the most local tag is
> > returned.
>
> and
>
> > However, when optional argument LOCAL is non-nil, only return tags
> > specified at the headline.
>
> Best regards,
>
> Juan Manuel
>
> --
> --
> --
> Juan Manuel Macías
>
> https://juanmanuelmacias.com
>
> https://lunotipia.juanmanuelmacias.com
>
> https://gnutas.juanmanuelmacias.com
>
>

Have all the tags of a heading, with a tag hierarchy

[Cletip Cletip]

Hello everyone !

After multiple searches on the internet, I did not find the answer to my
question (which is the subject of this mail): when calling the
"org-get-tags" function, only the tags put on the heading, and not the
inherited tags, are retrieved. How can I get the inherited tags as well?
Does such a function already exist? Did I miss an essential variable?


Thanks in advance for your future answer.

Re: Tracking todo state changes AND automatically change to done when all children are done

[Cletip Cletip]

It's ok, I managed to find it, thanks

I realize that I also have the same mistake as him (Can’t expand minibuffer
to full frame).


I'm not good enough in emacs-lisp, but I hope it's not too complicated to
solve for you ^^.

Le ven. 5 août 2022 à 04:27, Ihor Radchenko  a écrit :

> Okay, I understand. Sorry for the duplicate, I didn't see this thread.
>
>
> No problem. It's not like that thread is obviously related. I found the
> relation in the root cause, after debugging.
>
> Also, I don't understand why, but when I click on it, no site is
>> accessible. I tried to remove the "@localhost", also nothing.
>> Do you know how to follow the thread ?
>
>
> Copy-paste the link manually? IDK. The link works on my side.
> I guess you can search "org-auto-repeat-maybe: error "Can’t expand
> minibuffer to full frame" and missing log note
> <https://list.orgmode.org/orgmode/871qu8ccvr.fsf@localhost/#r>" subject
> in https://list.orgmode.org/
>
> On Fri, Aug 5, 2022 at 10:11 AM Cletip Cletip 
> wrote:
>
>> Okay, I understand. Sorry for the duplicate, I didn't see this thread.
>>
>> Also, I don't understand why, but when I click on it, no site is
>> accessible. I tried to remove the "@localhost", also nothing.
>> Do you know how to follow the thread ?
>>
>> Thanks you again for your help.
>>
>> On Fri, 5 Aug 2022, 03:26 Ihor Radchenko,  wrote:
>>
>>> Cletip Cletip  writes:
>>>
>>> > So, can we consider this as a bug?
>>>
>>> Yup. And the linked thread may be the fix or at least something close.
>>>
>>> Best,
>>> Ihor
>>>
>>>

Re: Tracking todo state changes AND automatically change to done when all children are done

[Cletip Cletip]

Okay, I understand. Sorry for the duplicate, I didn't see this thread.

Also, I don't understand why, but when I click on it, no site is
accessible. I tried to remove the "@localhost", also nothing.
Do you know how to follow the thread ?

Thanks you again for your help.

On Fri, 5 Aug 2022, 03:26 Ihor Radchenko,  wrote:

> Cletip Cletip  writes:
>
> > So, can we consider this as a bug?
>
> Yup. And the linked thread may be the fix or at least something close.
>
> Best,
> Ihor
>
>

Re: Tracking todo state changes AND automatically change to done when all children are done

[Cletip Cletip]

So, can we consider this as a bug?

Le jeu. 4 août 2022 à 17:01, Ihor Radchenko  a écrit :

> Cletip Cletip  writes:
>
> > Hello to all,
> >
> > I am trying to do what is in the title of this mail, but there is
> something
> > surprising:
> >
> > Everything works perfectly well, except when inserting statistics cookies
> > (for the parent obviously). Indeed, when changing the state of the
> subtask,
> > the lines like this :
> >
> > - State " new state" from "old state" [2022-08-04 Thu 16:09]
> >
> > are not saved under the subtask, but always under the main heading.
>
> This is likely related to
> https://orgmode.org/list/871qu8ccvr.fsf@localhost
> CCing Bhavin.
>
> > To reproduce this curious behavior, you only need this configuration:
>
> Confirmed.
>
> Something inside `org-todo' call in the hook triggers recursive-edit
> that, in turn, triggers premature call to post-command-hook containing
> note saving function.
>
> Best,
> Ihor
>

Tracking todo state changes AND automatically change to done when all children are done

[Cletip Cletip]

Hello to all,

I am trying to do what is in the title of this mail, but there is something
surprising:

Everything works perfectly well, except when inserting statistics cookies
(for the parent obviously). Indeed, when changing the state of the subtask,
the lines like this :

- State " new state" from "old state" [2022-08-04 Thu 16:09]

are not saved under the subtask, but always under the main heading.

To reproduce this curious behavior, you only need this configuration:

  (setq org-todo-keywords
'((sequence "TODO(t!)" "|" "DONE(d!)" )))

  (defun org-summary-todo (n-done n-not-done)
"Switch entry to DONE when all subentries are done, to TODO otherwise."
(let (org-log-done org-log-states) ; turn off logging
  (org-todo (if (= n-not-done 0) "DONE" "TODO"

  (add-hook 'org-after-todo-statistics-hook 'org-summary-todo)

;;(setq org-log-into-drawer t) ;;to have a logbook


and try on an org document like this one:


* TODO heading [0/1]

- State "DONE" from "TODO" [2022-08-04 Thu 16:09]

** TODO change the state of this heading !


My org-mode version is 9.5.2 (release_9.5.2-25-gaf6f12 @
/usr/share/emacs/28.1/lisp/org/).


Thank you in advance for your answers

Re: [PATCH] Re: Org-attach for a directory

[Cletip Cletip]

Thank you!

On Thu, 21 Jul 2022, 13:23 Ihor Radchenko,  wrote:

> Ihor Radchenko  writes:
>
> > As for the 'cp method, it does not work for directories on current main.
> > The fix is attached.
>
> Applied onto main via d2a110ffe.
>
> Best,
> Ihor
>

How to add/delete statistics cookie automatically ?

[Cletip Cletip]

Hello everyone,
My question is in the title, but for more detail on its exact use :

I'd like to add [/] or [%] to a parent heading in case I either add a TODO
subheading or a checkbox. I don't want to type it in the parent heading,
but add it automatically. Also, if all subheadings/checkboxes are removed,
the statistics cookie should be removed from the parent heading
automatically.

Question largely inspired by this one (which has not been answered):
https://www.reddit.com/r/emacs/comments/g2arww/how_to_adddelete_statistics_cookie_automatically/

Maybe this question is answered quite simply by having a correct level in
Lisp, but I still have a lot of trouble with this language. If someone
could help me, it would help me a lot ^^.

Thanks in advance for your future answers.

Re: Utility of description lists

[Cletip Cletip]

Ok I understand, it's really nice (the rendering on your site too).
Thanks for your answer

Le ven. 17 juin 2022 à 16:05, Kaushal Modi  a
écrit :

> On Fri, Jun 17, 2022 at 8:50 AM Cletip Cletip 
> wrote:
>
> > Final question : why do you use description lists and not another ?
>
> I use description lists *heavily*.
>
> 1. For description lists of course.. where the "description" part is a
> bit verbose and plain lists don't look at that elegant
>
> For example, this in Org
>
> =
> ** Customizing ~local.mk~ (Optional)
> Here are few variables that you might like to change in the ~local.mk~:
> - ~prefix~ :: Org installation directory
>   #+begin_src makefile
>   prefix = /dir/where/you/want/to/install/org # Default: /usr/share
>   #+end_src
>   The ~.el~ files will go to ~$(prefix)/emacs/site-lisp/org~ by
>   default. If you'd like to change that, change the ~lispdir~
>   variable too.
> - ~infodir~ :: Org Info installation directory. I like to keep the
>   Info file for development version of Org in a separate directory.
>   #+begin_src makefile
>   infodir = $(prefix)/org/info # Default: $(prefix)/info
>   #+end_src
> - ~ORG_MAKE_DOC~ :: Types of Org documentation you'd like to build by
>   default.  Setting below generates only the Org Info manual.
>   #+begin_src makefile
>   ORG_MAKE_DOC = info # Default: html pdf
>   #+end_src
> =
>
> exports to
> https://scripter.co/building-org-development-version/#customizing-local-dot-mk--optional
>
> 2. Where something would belong in a sub-heading, but not quite
> exactly? I can only describe that using one of my examples:
>
> =
> * Using ~pip install~
> If you do not want to manually download the ~.jar~, there's a Python
> wrapper available to do the same for you:
> [[https://github.com/svenkreiss/html5validator][html5validator]].
> - Install ::
>   #+begin_src shell
>   pip install --user html5validator
>   #+end_src
> - Run ::
>   #+begin_src shell
>   html5validator --root public/
>   #+end_src
>   It seems like this Python wrapper implicitly passes ~--skip-non-html
> =
>
> exports to https://scripter.co/offline-html5-validator/#using-pip-install
>
> 3. Sometimes I also use it for adding Notes to a section
>
> =
> - Note :: While the =%.1f= format is handy for those who are used to
>   =printf()= syntax, note that Calc unlimited precision
>   numbers are converted to double floats before applying
>   =%.1f=. Whereas =f1= operates on Calc numbers without
>   conversion.
> =
>
> exports to the Note in
> https://scripter.co/field-formatters-in-org-table/#using-calc-f1-formatter
>

Re: Utility of description lists

[Cletip Cletip]

Ok clear thanks!

Le ven. 17 juin 2022 à 15:43, Fraga, Eric  a écrit :

> On Friday, 17 Jun 2022 at 09:35, William Denton wrote:
> > When I have a list of things I want to briefly descibe!
>
> And where the leading bullet or number would simple add clutter.
> --
> : Eric S Fraga, with org release_9.5.4-535-ged6f8d in Emacs 29.0.50

Re: Utility of description lists

[Cletip Cletip]

Simple and efficient, thanks for your answer!


Le ven. 17 juin 2022 à 15:36, William Denton  a écrit :

> On 17 June 2022, Cletip Cletip wrote:
>
> > Final question : why do you use description lists and not another ?
>
> When I have a list of things I want to briefly descibe!  That's all.  It's
> just
> a way of formatting a list of things where there's a term (a word, a name,
> a
> title) that has some descriptive text.  Sometimes I use them when there's
> an
> obvious term/description pairing, and sometimes when I have a text-heavy
> list of
> things and I want to have a brief summary of each to make it easier to
> read.
>
>
> Bill
>
> --
> William Denton
> https://www.miskatonic.org/
> Librarian, artist and licensed private investigator.
> Toronto, Canada
>

Utility of description lists

[Cletip Cletip]

Hello to all,
The question is the same as the object, but it can be more detailed with
this question: what are the differences between description lists and other
lists?
After many researches, I can't understand the fundamental difference.
I can see two advantages to using this type of list:
- they are made implicitly to make a "key :: value" couple, which can be
convenient
- they can be useful when exporting: they have a different style than other
lists and can be used for some other things.

For example, with the use of org-roam (or even org-normal), if I want to
export a note with properties containing a link, I can't (the link is badly
exported). You can try with the following document :

:PROPERTIES:
:ID: 20220617115633324937
:SOURCE: [[id:20220617105453042719][Emacs]]
:CITE: [cite:@DifferenceSemantiqueEntre2022]
:END:
#+title: Test Page
#+OPTIONS: prop:t


- cite :: [cite:@DifferenceSemantiqueEntre2022]
- source :: [[id:20220617105453042719][Emacs]]

* Title and some content after here



Morehover, this type of data can be exploited by the Vulpea library (
https://github.com/d12frosted/vulpea), which could allow to add other
information to each note.

Final question : why do you use description lists and not another ?

PS : Thank you very much in advance for your future response, I discover
this original system to ask questions and I hope not to abuse it by asking
this type of questions ^^

Re: Org-attach for a directory

[Cletip Cletip]

Thank you for your answer.
Unfortunately, I would like to copy the entire directory.
To clarify my second question, I would like to have a folder system with
org-mode, and therefore only use org-attach to store my documents

Le mer. 8 juin 2022 à 12:27, Fraga, Eric  a écrit :

> On Wednesday,  8 Jun 2022 at 11:59, Cletip Cletip wrote:
> > My question is in the object : can we attach a directory to a heading?
>
> If you mean copying the directory and all of its contents, I imagine
> not.  However, you can link to the directory if you wish by visiting the
> directory using dired, say, and storing the link (org-store-link).  The
> link can then be inserted wherever you wish using org-insert-link.
> Alternatively, you could also tar or zip up the contents of the
> directory and attach that.
>
> > Subsidiary question:
> > Can we use org-attach as a filesystem?
>
> What is it you wish to do?  I do not understand this question.
>
> --
> : Eric S Fraga, with org release_9.5.4-521-g1105da in Emacs 29.0.50

Org-attach for a directory

[Cletip Cletip]

Hello to all.
I hope to have understood the operation to ask a question to all the
members, I hope that my question will not disturb anybody.
If this is not the right place, do not hesitate to tell me and I apologize
in advance for the inconvenience

My question is in the object : can we attach a directory to a heading?
If yes, how, if not, why. Can we solve the problem?

Subsidiary question:
Can we use org-attach as a filesystem?
Thanks in advance for your future answers

[BUG] org-icalendar-combined-agenda-file with Footnotes [9.4.6 (9.4.6-g069bcb @ /home/msi/.emacs.d/straight/build/org/)]

[Cletip Cletip]

When I call the "org-icalendar-combined-agenda-file" function,
everything works fine, I have a new "file.ics". But if you try to make
footnotes in one of the files (in org-agenda-files) taken into account in
the
org-icalendar-combined-agenda-file function, look at the end of the
resulting file "file.ics" : the footnotes are included in the .ics file,
which obviously creates a bug in the file


Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.20, cairo version 1.16.0)
 of 2020-09-19
Package: Org mode version 9.4.6 (9.4.6-g069bcb @
/home/msi/.emacs.d/straight/build/org/)