From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: Chong Yidong <cyd@stupidchicken.com>,
8463@debbugs.gnu.org, Leo <sdl.web@gmail.com>
Subject: bug#8463: 24.0.50; [PATCH] Direct Edit in *Occur* Buffer
Date: Mon, 13 Jun 2011 02:10:07 +0300 [thread overview]
Message-ID: <BANLkTikgqBcBrBZyWzjzBYCco+BBRbqNzg@mail.gmail.com> (raw)
In-Reply-To: <87vcwctfig.fsf@mail.jurta.org>
On Sat, Jun 11, 2011 at 21:00, Juri Linkov <juri@jurta.org> wrote:
>>>> Or "e" (for edit; like in Rmail).
>>>
>>> That sounds good.
>>
>> But not for case, when user already switched the *Occur* buffer into
>> read/write mode for editing the buffer itself (not the underlying
>> files/buffers, where occurrences come from).
>
> Then maybe `M-e' (like in isearch mode)?
If separate apply-changes-to-underlying-buffers action to the own
function (may be even it already implemented in that way) then all
controversy will gone. -- Enter to read-write mode -- the same,
editing commands -- the same, all other behavior -- the same. Just
because there will work one and the same code in the one and the same
mode. Difference is only one between my usage model and usage model
of Leo (original author) -- after finishing I simple kill the occur
buffer, while Leo call the "apply-cachanges-to-underlying-buffers" for
"commit" the final results.
IMHO anyone can benefit from solving the problem in that way.
--
Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
next prev parent reply other threads:[~2011-06-12 23:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 8:14 bug#8463: 24.0.50; [PATCH] Direct Edit in *Occur* Buffer Leo
2011-04-15 1:11 ` Stefan Monnier
2011-05-28 23:05 ` Chong Yidong
2011-05-29 4:04 ` Leo
2011-05-30 14:04 ` Andrew W. Nosenko
2011-05-30 23:10 ` Richard Stallman
2011-06-01 23:03 ` Glenn Morris
2011-06-03 2:36 ` Leo
2011-06-03 15:38 ` Stefan Monnier
2011-06-04 21:34 ` Chong Yidong
2011-06-05 9:30 ` Štěpán Němec
2011-06-06 15:34 ` Stefan Monnier
2011-06-09 4:47 ` Leo
2011-06-09 5:14 ` Glenn Morris
2011-06-09 9:44 ` Leo
2011-06-09 9:54 ` Eli Zaretskii
2011-06-09 9:58 ` Leo
2011-06-09 9:42 ` Leo
2011-06-09 18:09 ` Glenn Morris
2011-06-10 13:59 ` Stefan Monnier
2011-06-10 16:14 ` Ted Zlatanov
2011-06-11 9:58 ` Andrew W. Nosenko
2011-06-11 18:00 ` Juri Linkov
2011-06-12 23:10 ` Andrew W. Nosenko [this message]
2011-06-18 19:35 ` Chong Yidong
2011-06-18 20:36 ` Andrew W. Nosenko
2011-09-09 11:39 ` Juri Linkov
2011-09-14 19:04 ` Juri Linkov
2011-09-17 21:28 ` Chong Yidong
2011-09-18 19:33 ` Juri Linkov
2011-09-19 18:52 ` Chong Yidong
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikgqBcBrBZyWzjzBYCco+BBRbqNzg@mail.gmail.com \
--to=andrew.w.nosenko@gmail.com \
--cc=8463@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=juri@jurta.org \
--cc=sdl.web@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).