From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Preventing inadvertent global modifications
Date: Fri, 15 Sep 2023 18:00:11 +0700 [thread overview]
Message-ID: <ue1dft$15m0$1@ciao.gmane.io> (raw)
In-Reply-To: <87msxoc3qp.fsf@localhost>
On 14/09/2023 19:56, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> C-u C-c C-q still realigns all tags in the buffer, so this option would
>> not save me from getting huge diff.
>
> C-u C-c C-q is explicitly documented to do so. Surely, you may press
> universal argument by accident, but so you do for, say, C-u C-u C-k,
> deleting 16 lines at once. I am not sure if makes much sense to
> intervene here.
I have never tried to dispute that it is documented.
The issue is not prefix argument and not namely aligning tags, but a lot
of modifications scattered across file being invisible in the active frame.
I do not remember if I had problems due to C-k, but adding some friction
to C-w and M-w if the mark is too far away is in my plan. Fortunately I
usually can notice that C-w deletes significant part of my file because
mark was set in other window. So undo helps (attention is required
however to not revert undo to redo and to stop at proper point). Since
adjacent region may be unfolded in response to editing action, sometimes
it is hard to figure out if effect of key hit is consistent with
expectations.
> I am reluctant (see the above), unless other users also think that such
> feature would be useful.
Since nobody joined to the thread, I assume it is my personal pain,
perhaps related to Vim, perhaps to other experience. I can not say that
I am investing noticeable amount of efforts to eliminate it, but I hope
I will get better ideas in future.
prev parent reply other threads:[~2023-09-15 11:01 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
2023-09-14 12:56 ` Ihor Radchenko
2023-09-15 11:00 ` Max Nikulin [this message]
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='ue1dft$15m0$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).