From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Juri Linkov <juri@jurta.org>
Cc: Deniz Dogan <deniz.a.m.dogan@gmail.com>,
Wojciech Meyer <wojciech.meyer@googlemail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Refreshing Info nodes
Date: Wed, 16 Jun 2010 00:38:18 +0100 [thread overview]
Message-ID: <87bpbbkgt1.fsf@gmail.com> (raw)
In-Reply-To: <87hbl4kn77.fsf@mail.jurta.org> (Juri Linkov's message of "Wed, 16 Jun 2010 00:35:12 +0300")
Juri Linkov <juri@jurta.org> writes:
>> I think back(last)/up/g/j should be consistent in at least these modes:
>>
>> "help" buffer
>> dired
>> info
>> w3m
>
> back(last) up goto revert
> dired q ^ j g
> info l u g -
> help C-c C-b ? ? -
Yes, I found those inconsistencies too. Info node could be crossed out
from the list of candidates to change as bare info uses traditional
keymap (like Eli mentioned), however the package could provide a
different alternative set of bindings compatible with the rest of Emacs
(I agree that none of Emacs packages uses that approach, usually there
is one keymap, and it is up to the user to rebind it, but in this case
we would enforce at least optional consistency with other packages, and
for me it would be OK to change the default mode to the `right way to do
it in Emacs'. it is a good compromise). However in case of dired, help,
vc and any other mode for navigation over some *hierarchical* entity
that should be *synchronised* with some external state (the most common
is file-system -> dired), this should be unified. (one base mode for it?
I've noticed that we can inherit major modes).
BTW: I found that vc-status could be pretty much similar to dired. Would
that be feasible to annotate files in dired and shift some functionality
from vc-status mode to dired? (Most of the time I spent in dired anyway,
and calling vs status, or having a feedback about status of files under
version control could be good. (I know again, dired uses ls -l format
for historicial reasons, and there will be maybe a good lag during
updating the buffer, but...)
Just mine two cents,
Thanks.
Wojciech
next prev parent reply other threads:[~2010-06-15 23:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 17:51 Refreshing Info nodes Wojciech Meyer
2010-06-13 17:56 ` Deniz Dogan
2010-06-14 15:38 ` Juri Linkov
2010-06-14 18:34 ` Wojciech Meyer
2010-06-14 19:08 ` Stefan Monnier
2010-06-14 20:49 ` joakim
2010-06-14 21:59 ` Juri Linkov
2010-06-14 22:58 ` joakim
2010-06-15 21:35 ` Juri Linkov
2010-06-15 23:38 ` Wojciech Meyer [this message]
2010-06-16 13:39 ` Stefan Monnier
2010-06-16 20:43 ` Juri Linkov
2010-06-17 0:46 ` Stefan Monnier
2010-06-17 8:29 ` Juri Linkov
2010-08-28 20:38 ` Wojciech Meyer
2010-08-28 20:50 ` Eli Zaretskii
2010-08-28 22:17 ` Wojciech Meyer
2010-08-29 15:18 ` Wojciech Meyer
2010-09-11 13:19 ` Stefan Monnier
2010-09-11 14:00 ` Wojciech Meyer
2010-09-13 1:34 ` Wojciech Meyer
2010-09-13 10:11 ` Stefan Monnier
2010-09-13 10:22 ` Wojciech Meyer
2010-06-17 8:00 ` Richard Stallman
2010-06-17 8:52 ` Wojciech Meyer
2010-06-15 0:38 ` Stefan Monnier
2010-06-16 20:35 ` Juri Linkov
2010-06-17 0:49 ` Stefan Monnier
2010-06-15 3:00 ` Eli Zaretskii
2010-06-15 3:18 ` Drew Adams
2010-06-14 21:57 ` Juri Linkov
2010-06-15 0:42 ` Stefan Monnier
2010-06-16 20:33 ` Juri Linkov
2010-06-17 0:50 ` Stefan Monnier
2010-06-17 20:34 ` Juri Linkov
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=87bpbbkgt1.fsf@gmail.com \
--to=wojciech.meyer@googlemail.com \
--cc=deniz.a.m.dogan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
/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.