gnus-mime-*-part vs. the keys they mask

gnus-mime-*-part vs. the keys they mask

[jidanni]

Of
RET gnus-article-press-button
C-o gnus-mime-save-part-and-strip
. gnus-mime-action-on-part
C gnus-mime-view-part-as-charset
E gnus-mime-view-part-internally
c gnus-mime-copy-part
d gnus-mime-delete-part
e gnus-mime-view-part-externally
i gnus-mime-inline-part
o gnus-mime-save-part
p gnus-mime-print-part
t gnus-mime-view-part-as-type
v gnus-mime-view-part
| gnus-mime-pipe-part

I have a big problem with "p". You see when we hit p, we expect it is
part of the usual n/p pair: gnus-summary-prev-unread-article. However
surprise surprise, we discover the cursor just happens to be resting
on a mime part marker, as we hear the printer upstairs in Mom's room
churning out our um, sensitive image.

Re: gnus-mime-*-part vs. the keys they mask

[Ted Zlatanov]

On Wed, 15 Oct 2008 06:18:49 +0800 jidanni@jidanni.org wrote: 

j> Of
j> RET gnus-article-press-button
j> C-o gnus-mime-save-part-and-strip
j> . gnus-mime-action-on-part
j> C gnus-mime-view-part-as-charset
j> E gnus-mime-view-part-internally
j> c gnus-mime-copy-part
j> d gnus-mime-delete-part
j> e gnus-mime-view-part-externally
j> i gnus-mime-inline-part
j> o gnus-mime-save-part
j> p gnus-mime-print-part
j> t gnus-mime-view-part-as-type
j> v gnus-mime-view-part
j> | gnus-mime-pipe-part

j> I have a big problem with "p". You see when we hit p, we expect it is
j> part of the usual n/p pair: gnus-summary-prev-unread-article. 

Perhaps it should be 'P'?

j> However surprise surprise, we discover the cursor just happens to be
j> resting on a mime part marker, as we hear the printer upstairs in
j> Mom's room churning out our um, sensitive image.

Based on your bug scenarios, you lead a very frustrating life (cf. the
report in RISKS where you accidentally launched missiles, etc.).

Ted

Re: gnus-mime-*-part vs. the keys they mask

[Reiner Steib]

On Wed, Oct 15 2008, Ted Zlatanov wrote:

> On Wed, 15 Oct 2008 06:18:49 +0800 jidanni@jidanni.org wrote: 
[...]
> j> d gnus-mime-delete-part
> j> e gnus-mime-view-part-externally
> j> i gnus-mime-inline-part
> j> o gnus-mime-save-part
> j> p gnus-mime-print-part
[...]
> j> I have a big problem with "p". You see when we hit p, we expect it is
> j> part of the usual n/p pair: gnus-summary-prev-unread-article. 
>
> Perhaps it should be 'P'?

No, we shouldn't change long established key bindings just because
jidanni seems to be in the habit of hitting the wrong keys (cf. the
discussion on `C-c C-c').  Several of the other bindings also have
valid normal summary bindings (e.g. d, o, ...).  Every user can
change/unset the key binding in his init files.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: gnus-mime-*-part vs. the keys they mask

[jidanni]

j> p gnus-mime-print-part

TZ> Perhaps it should be 'P'?

But that would mask gnus-summary-prev-article.

  p runs the command gnus-mime-print-part
  It is bound to p, <menu-bar> <MIME Part> <Print>.

maybe just <menu-bar> <MIME Part> <Print> is enough?

Say, perhaps all the gnus-mime- keys should have their own prefix
keymap, and the more dangerous/conflicting(with the underlying keymap)
ones could be moved there.

TZ> Based on your bug scenarios, you lead a very frustrating life (cf. the
TZ> report in RISKS where you accidentally launched missiles, etc.).

Well at least I haven't started a forest fire, yet.

Re: gnus-mime-*-part vs. the keys they mask

[Ted Zlatanov]

On Thu, 16 Oct 2008 05:49:50 +0800 jidanni@jidanni.org wrote: 

j> p gnus-mime-print-part
TZ> Perhaps it should be 'P'?

j> But that would mask gnus-summary-prev-article.

I think we'll leave it alone, as Reiner suggested.  You can remap them
if it bothers you, but I think for the Gnus users in general it's OK.

j>   p runs the command gnus-mime-print-part
j>   It is bound to p, <menu-bar> <MIME Part> <Print>.

j> maybe just <menu-bar> <MIME Part> <Print> is enough?

j> Say, perhaps all the gnus-mime- keys should have their own prefix
j> keymap, and the more dangerous/conflicting(with the underlying keymap)
j> ones could be moved there.

I think it's really a 50-50 decision, and I'll go with Reiner on it,
leaving things alone.

Ted