From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: New feature? Remove duplicate subheadings, preserving order
Date: Tue, 02 Jan 2018 11:36:28 -0500 [thread overview]
Message-ID: <87r2r8w73n.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CAJr1M6dpbWzqMViNQBZ5O6F2Ht66HR_FTZE8KZ8dC8LiMsquGg@mail.gmail.com
Allen Li <vianchielfaura@gmail.com> writes:
>
> I don’t see a use case for checking all heading data.
>
>>> Since the point would be remove duplicates from lists, I don’t think
>>> warning is very useful. I would want to remove the duplicate list
>>> items, not get a warning about it and delete them manually. Perhaps
>>> that would be a useful additional feature however (like uniq -d).
>>
>> I think warning or asking for confirmation should be the default action,
>> because it's the safest option. Users who want to skip that could use a
>> prefix argument or call it from a custom command.
>
> There is always undo and automatic Emacs file backups.
>
There be dragons.
The problem is that some things happen invisibly and far away from
where you are, so you don't know about it and you don't find out for a
couple of weeks. Undo and automatic backups are useless in that case.
That *has* happened: there have been multiple postings in the ML about
such problems. Whenever it has happened, the devs have always modified
org to make it safer: that is the prudent thing to do and the correct
course of action IMO.
Hell hath no fury like an orgmode user who lost part of his/her
precious org file because of an errant keystroke a month ago and was
not aware of the loss until it was too late.
--
Nick
next prev parent reply other threads:[~2018-01-02 16:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 2:42 New feature? Remove duplicate subheadings, preserving order Allen Li
2018-01-01 5:55 ` Marcin Borkowski
2018-01-01 10:04 ` Nicolas Goaziou
2018-01-01 11:59 ` Allen Li
2018-01-01 18:26 ` Nicolas Goaziou
2018-01-01 23:04 ` Allen Li
2018-01-02 4:07 ` Adam Porter
2018-01-02 7:40 ` Allen Li
2018-01-02 14:36 ` Robert Horn
2018-01-02 21:34 ` Allen Li
2018-01-02 16:36 ` Nick Dokos [this message]
2018-01-02 21:22 ` Allen Li
2018-01-03 7:24 ` Adam Porter
2018-01-03 7:40 ` Adam Porter
2018-01-03 8:19 ` Ihor Radchenko
2018-01-03 9:39 ` Adam Porter
2018-01-02 15:28 ` Florian Beck
2018-01-02 21:28 ` Allen Li
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=87r2r8w73n.fsf@alphaville.usersys.redhat.com \
--to=ndokos@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).