emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Rename headline to heading
Date: Sun, 15 Aug 2021 08:54:40 +1000	[thread overview]
Message-ID: <87v947wr7s.fsf@gmail.com> (raw)
In-Reply-To: <segul5$l04$1@ciao.gmane.io>


Maxim Nikulin <manikulin@gmail.com> writes:

> On 05/08/2021 19:12, André A. Gomes wrote:
>> @@ -963,7 +963,7 @@ Store them in the capture property list."
>>   	    (org-capture-put-target-region-and-position)
>>   	    (goto-char position))
>>   	   (_ (error "Cannot find target ID \"%s\"" id))))
>> -	(`(file+headline ,path ,headline)
>> +	(`(file+heading ,path ,heading)
>
> I am sorry if is a false alarm. Does it mean that all users having
> "file+headline" in their init.el files will have to immediately update
> configuration? Shouldn't both variants be supported during transitional period?
>
> P.S. https://orgmode.org/worg/dev/org-syntax.html consistently uses "headline".

I'm not convinced a transition period will help in this case. At some
point, users will need to update their capture templates regardless.
Provided this impact is clearly outlined in the NEWS.org file (I think
there should be a specific reference to capture templates added in the
patch to NEWS.org) and provided this change is applied to the next
release only, no transition period is necessary.

In this case, a transition period would add complexity to the code that
would have to remain in place until the next major release and at that
release, anyone who has not updated their templates will have the same
breakage anyway. I feel there is a difference between changes in
configuration and changes in code. Updating capture templates is
trivial. Updating code is often more complex, which is why we have the
obsolete mechanism for functions and variables. 

If we were making this change in a maintenance release, that would be a
completely different story and a transition period would definitely be
necessary. Users should expect some breakage in configuration when
upgrading to a new major version. 


  reply	other threads:[~2021-08-14 23:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 12:12 [PATCH] Rename headline to heading André A. Gomes
2021-08-05 15:04 ` Maxim Nikulin
2021-08-14 22:54   ` Tim Cross [this message]
2021-08-15 16:22     ` No Wayman
2021-08-15 16:50       ` No Wayman
2021-08-15 22:32     ` Jim Porter
2021-08-15 23:17       ` Tim Cross
2021-08-16  0:38         ` Jim Porter
2021-08-16  1:18           ` Tim Cross
2021-08-08 16:59 ` Tom Gillespie
2021-08-14 23:19 ` Tim Cross
2021-09-19 11:06 ` Timothy
2021-09-30 12:08   ` André A. Gomes
2021-09-26  9:27 ` Bastien
2021-09-30 12:21   ` André A. Gomes
2021-10-01  8:38     ` Bastien
2021-10-15  8:52       ` André A. Gomes
2021-10-15  9:56         ` Timothy
2021-10-15 10:18           ` André A. Gomes

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=87v947wr7s.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).