From: Mauro Aranda <maurooaranda@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Lennart Borgman <lennart.borgman@gmail.com>,
6419@debbugs.gnu.org
Subject: bug#6419: A suggestion for easier editing of lists in Custom buffers
Date: Wed, 21 Oct 2020 15:05:36 -0300 [thread overview]
Message-ID: <CABczVwesfzkrtyMQHNpkPX5mzy2ZfiV+_JEQfsxBeTM6idm5vQ@mail.gmail.com> (raw)
In-Reply-To: <1788f78e-28f4-466d-9f8c-539f1896348f@default>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Drew Adams <drew.adams@oracle.com> writes:
>>> Should "a previously deleted one" be "the last-deleted one"?
>>
>> Not necessarily. It works like a stack.
>
> How is that different - LIFO, no?
> In any case, how it works needs to be made clear
> somewhere.
Yes, of course. But in that case I think the help-echo should say
explicitly: "the last-deleted one not yet reinserted", or something like
that.
>>> If you use INS in one customize buffer after using
>>> DEL in another, or after using DEL in another part
>>> of the same buffer (but not part of the same sequence),
>>> is that last-deleted item inserted? Or is it only the
>>> last-deleted (if any) from the same sequence?
>>
>> The latter. This only implements moving items within the same
> sequence.
>
> So maybe make that clear somehow.
Will try.
[-- Attachment #2: Type: text/html, Size: 1094 bytes --]
next prev parent reply other threads:[~2020-10-21 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 5:47 bug#6419: A suggestion for easier editing of lists in Custom buffers Lennart Borgman
2020-10-14 12:14 ` Mauro Aranda
2020-10-16 5:09 ` Lars Ingebrigtsen
2020-10-21 15:37 ` Mauro Aranda
2020-10-21 17:03 ` Drew Adams
2020-10-21 17:32 ` Mauro Aranda
2020-10-21 17:48 ` Drew Adams
2020-10-21 18:05 ` Mauro Aranda [this message]
2020-10-22 11:38 ` Lars Ingebrigtsen
2020-10-22 11:48 ` Mauro Aranda
2020-10-22 11:54 ` Lars Ingebrigtsen
2020-10-22 12:03 ` Mauro Aranda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABczVwesfzkrtyMQHNpkPX5mzy2ZfiV+_JEQfsxBeTM6idm5vQ@mail.gmail.com \
--to=maurooaranda@gmail.com \
--cc=6419@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=lennart.borgman@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.