From: Ihor Radchenko <yantar92@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Org-mode <emacs-orgmode@gnu.org>,
Daniel Mendler <mail@daniel-mendler.de>
Subject: [STYLE] :version tags in defcustom definitions (was: [PATCH] Improve look of agenda on graphical displays)
Date: Wed, 29 Jun 2022 20:46:38 +0800 [thread overview]
Message-ID: <87fsjnk575.fsf@localhost> (raw)
In-Reply-To: <CADwFkmk1mYV7Z8Z3ifKFD4cv-4shJxAQGc5XEmHcVmcU5GWXGQ@mail.gmail.com>
Stefan Kangas <stefan@marxist.se> writes:
>> I am wondering if this is meaningful considering that Org is not always
>> distributed together with Emacs. Will this :version tag make any sense
>> for people using the newest Org with older Emacs versions?
>
> I think it won't really, but that's okay. Also, this is how Org has
> used these tags historically, try grepping for ":version" to see.
I did try. Only ~40% of defcustoms are supplied with :version tags.
Also, ~75% of the tags were introduced long time ago: Emacs 24.
The rest, except the 4 (four in total) Emacs 27 are all Emacs 26.
> IOW, changing this is orthogonal to this patch.
Sure. Just trying to clarify my confusion. The inconsistency with some
defcustoms using :version and some not is bugging me.
Best,
Ihor
next prev parent reply other threads:[~2022-06-29 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:08 [PATCH] Improve look of agenda on graphical displays Stefan Kangas
2022-06-29 9:19 ` Ihor Radchenko
2022-06-29 10:20 ` Stefan Kangas
2022-06-29 12:46 ` Ihor Radchenko [this message]
2022-06-29 12:55 ` [STYLE] :version tags in defcustom definitions (was: [PATCH] Improve look of agenda on graphical displays) Stefan Kangas
2022-06-29 14:07 ` Timothy
2022-06-29 16:56 ` Bruce D'Arcus
2022-11-13 7:38 ` [PATCH] " Ihor Radchenko
2022-11-19 13:03 ` [PATCH] Re: [STYLE] :version tags in defcustom definitions Bastien Guerry
2022-11-20 5:47 ` Ihor Radchenko
2022-06-30 7:28 ` [PATCH] Improve look of agenda on graphical displays Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsjnk575.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@daniel-mendler.de \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).