From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Preventing inadvertent global modifications
Date: Wed, 13 Sep 2023 17:50:27 +0700 [thread overview]
Message-ID: <uds45k$qd3$1@ciao.gmane.io> (raw)
In-Reply-To: <87jzsuh55a.fsf@localhost>
On 13/09/2023 15:02, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> Yesterday, when I was going to commit changes after editing several
>> headings in different places of an Org file, I was surprised by huge
>> diff with hundreds of chunks. Tags spread across the whole file were
>> adjusted by one or tow spaces. Probably I just accidentally hit C-u
>> before setting a tag to a new heading by C-c C-q. Of course, I did not
>> noticed it immediately. I managed to create a commit with real changes
>> without noise due to tags realignment. However I would like to prevent
>> similar issues in future.
>
> You can set `org-auto-align-tags' to nil.
I saw it, but from its description I decided that its effect may be to
broad. I have tried it and to my surprise it does not affect editing of
heading, tags are kept aligned. M-<right> and M-<left> do not realign
tags, so the value is not ignored.
C-u C-c C-q still realigns all tags in the buffer, so this option would
not save me from getting huge diff.
I suspect there are enough commands having similar global (and so mostly
hidden) effect. I may be unaware of them because I do not feel that I
need such commands.
I admit that some fraction of users keep their files tidy calling C-u
C-c C-q regularly. Perhaps at certain moment I will decide no align
tags, but it should be a dedicated commit not mixed with other changes.
My opinion that, by default, commands performing massive changes should
require reasonable efforts to execute. It should help to avoid calling
them unintentionally. Perhaps there is a better approach than annoying
`yes-or-no-p'.
next prev parent reply other threads:[~2023-09-13 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:47 Preventing inadvertent global modifications Max Nikulin
2023-09-13 8:02 ` Ihor Radchenko
2023-09-13 10:50 ` Max Nikulin [this message]
2023-09-14 12:56 ` Ihor Radchenko
2023-09-15 11:00 ` Max Nikulin
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='uds45k$qd3$1@ciao.gmane.io' \
--to=manikulin@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).