-- Forwarded message --
From: David R
Date: Thursday, December 19, 2019
Subject: Properties Drawer versus tags
To: Lawrence Bottorff
On Thursday, December 19, 2019, Lawrence Bottorff wrote:
> Very simple, largely philosophical question: When/why use a properties
I forgot something important, part of "the case in favor of properties":
It's sometimes useful to be able to search for a category or sort by a
category. It's harder to do that if you haven't explicitly entered that
Very simple, largely philosophical question: When/why use a properties
drawer below a heading versus just using tags on the heading? What are the
advantages, disadvantages of both?
Dear Org developers,
I filed a bug report in Emacs debbugs, but probably should have sent it
The attached patch appears to fix the bug. Does it look OK?
>From 6102f07d61ee5d128701b7d3799b2e278aa79248 Mon Sep
Now that Org 9.3 has been released, I'd like to bring this issue up again.
On Wed, Sep 25, 2019 at 1:13 PM Robert Irelan wrote:
> The :link header argument on clock tables (see
> https://orgmode.org/manual/The-clock-table.html) currently generates
> links that use fuzzy search when `:link t` is
Ihor Radchenko writes:
> You can try M-x org-submit-bug-report ;)
> Then it becomes clear that you are in the right place already.
Thanks! I didn't know about this command - actually I had searched for
it but didn't find it because I had searched for something named
I want to suggest to make `report-org-bug' and alias for the command
`org-submit-bug-report'. That's the name I expected (considering
"report-emacs-bug"), also some other Emacs packages name their bug
reporting command according to this scheme. The additional name would
Samuel Wales writes:
> the indirect buffer capture mechanism was to be an improvement on
> remember.el, and replaced it. you might still be able to find
> remember.el if you prefer the separate file idea.
I find it acceptable once it's been made more secure (e.g. by using
hooks like I
Adam Porter writes:
> People do care! But everyone here works on Org in their spare time,
> and Org is a big project, and things slip through the cracks.
I didn't meant to criticize anyone (I have the same problem with my own
stuff). Anyway, we got some attention now, thanks for your help!
> I did not need to add this line to confirm the behavior:
>> (push (cons "el" "src emacs-lisp") org-structure-template-alist)
Note the 5.2 part of the recipe.
It is probably caused by the same reason, but the consequence is that
the following code block is being commented, sometimes out of the
Matt Price writes:
> Ah, interesting. That makes a lot of sense. Would it be unworkably
> destructive for me to revert the link syntax locally ? I have no particular
> need for the new functionality and the current situation has been a
> significant cognitive burden, not least because
Tom Gillespie writes:
> Subject: org.el: Fix verbatim block fontification to end blocks on
Applied. Thank you.
I added TINYCHANGE cookie at the end of your commit message since I do
not know if you have signed FSF papers already. If you did, please let
me know so I can
On Thu, Dec 19, 2019 at 2:55 AM Nicolas Goaziou
> Matt Price writes:
> > MWE:
> > test.org:
> > --
> > This is a paragraph with [[https://google.com][a link]]
> > ---
> > steps to reproduce:
> > put cursor at beginning of file and type ~[[~. The paragraph text will
Ezequiel Birman writes:
> Hi all.
> use a session managed via
> https://github.com/NicolasPetton/Indium is currently
> I believe the error I am getting is related to
A quick test has proved to me that org-conflict is able to do exactly what
I want it to - in fact, it's much better than I had imagined, with useful
features I hadn't thought of.
Now, if I turn out to be smart enough to make it run properly on all my Org
files, I'll be extremely happy with the
Mail list logo