From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>
To: "Juri Linkov" <juri@jurta.org>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org
Subject: Re: Finding the source of Change Log entries
Date: Tue, 15 Jul 2008 09:23:27 +0300 [thread overview]
Message-ID: <6161f3180807142323w75acebb1m503d7754a5500cfa@mail.gmail.com> (raw)
In-Reply-To: <87y744jfnc.fsf@jurta.org>
On Tue, Jul 15, 2008 at 12:54 AM, Juri Linkov <juri@jurta.org> wrote:
>> CY> Also, instead of binding change-log-find-tag to C-c C-t, how about using
>> CY> C-c C-c for consistency with diff-mode? (You might also want to rename
>> CY> change-log-find-tag to change-log-goto-source for consistency with
>> CY> diff-goto-source, but that's your call.)
>>
>> Would it be acceptable to bind next-error and previous-error in this
>> mode, so users could use them to navigate between points of interest in
>> the ChangeLog, similar to error logs and grep/occur output?
>>
>> I'd find that really helpful, and can write the glue code necessary.
>
> I think it would be a good thing, and this could be implemented
> on top of Martin's code.
Sorry, but I think that it would be the bad thing because could to
block regular C-x` usage just because my current (or last visited)
file was in ChangeLog mode... Please, do not do this, or, if it
really needed for someone, keep it turned off by default.
--
Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
next prev parent reply other threads:[~2008-07-15 6:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 9:32 Finding the source of Change Log entries martin rudalics
2008-07-12 10:00 ` Lennart Borgman (gmail)
2008-07-12 10:32 ` martin rudalics
2008-07-12 14:52 ` Chong Yidong
2008-07-13 8:33 ` martin rudalics
2008-07-13 22:14 ` Juri Linkov
2008-07-14 8:40 ` martin rudalics
2008-07-14 21:57 ` Juri Linkov
2008-07-16 17:20 ` martin rudalics
2008-08-07 10:10 ` martin rudalics
2008-07-14 13:50 ` Ted Zlatanov
2008-07-14 21:54 ` Juri Linkov
2008-07-15 6:23 ` Andrew W. Nosenko [this message]
2008-07-15 9:48 ` Juri Linkov
2008-07-15 14:56 ` Ted Zlatanov
2008-07-15 20:35 ` Juri Linkov
2008-07-16 17:20 ` martin rudalics
2008-08-05 18:43 ` Ted Zlatanov
2008-08-25 15:43 ` Juri Linkov
2008-08-27 18:37 ` Ted Zlatanov
2008-08-27 20:43 ` Stefan Monnier
2008-08-27 20:57 ` Ted Zlatanov
2008-08-28 2:03 ` Stefan Monnier
2008-09-10 23:59 ` Juri Linkov
2008-09-14 11:27 ` martin rudalics
2008-07-14 14:00 ` Dan Nicolaescu
2008-07-16 17:18 ` martin rudalics
2008-07-27 21:47 ` Dan Nicolaescu
2008-07-28 18:50 ` martin rudalics
2008-07-28 21:53 ` Stefan Monnier
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=6161f3180807142323w75acebb1m503d7754a5500cfa@mail.gmail.com \
--to=andrew.w.nosenko@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=tzz@lifelogs.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).