Possible gnus bug when pressed 'C-u n'

Possible gnus bug when pressed 'C-u n'

[Borja Tarraso Hueso]

[-- Attachment #1.1: Type: text/plain, Size: 514 bytes --]

Hi people,

I don't know if this is an expected behaviour, but inside gnus when I
pressed "C-u #"  or "C-u !" etc... gnus marks the next 4 emails. However
this does not happens when is pressed "C-u n" or "C-u SPC", it only marks
next email, but not next 4. Is it expected? or is it a possible bug? In this
case should I open a case as an emacs bug/new feature? I think this command
should accept prefix arguments following the rest of cases. I will check
other prefix combinations as well.

Thanks!

Borja Tarraso

[-- Attachment #1.2: Type: text/html, Size: 583 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Possible gnus bug when pressed 'C-u n'

[Borja Tarraso Hueso]

[-- Attachment #1.1: Type: text/plain, Size: 1207 bytes --]

Hi Bill,

Yes, i understand that not everything uses the default prefix, but using
"C-10 n" does not work as I expected (read next emails or read the 10th
email) just always read next email. Also I understand that's not a bug if
the implementation of that does not take care about that, although i think
it could be good to do that as the rest of commands (in the same family -
"C-u #", etc) takes care of that.

Thanks!

Borja Tarraso

2009/5/29 Bill O'Connor <billyoc@gmail.com>

> Borja Tarraso Hueso <borja.tarraso.hueso@googlemail.com> writes:
>
> > Hi people,
> >
> > I don't know if this is an expected behaviour, but inside gnus when I
> pressed
> > "C-u #"  or "C-u !" etc... gnus marks the next 4 emails. However this
> does not
> > happens when is pressed "C-u n" or "C-u SPC", it only marks next email,
> but not
> > next 4. Is it expected? or is it a possible bug? In this case should I
> open a
> > case as an emacs bug/new feature? I think this command should accept
> prefix
> > arguments following the rest of cases. I will check other prefix
> combinations
> > as well.
>
> Four is the default prefix, and not everything uses the default prefix.
>
> --
> In Solidarity,
> Billy O'Connor
>

[-- Attachment #1.2: Type: text/html, Size: 1791 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Possible gnus bug when pressed 'C-u n'

[Ted Zlatanov]

On Mon, 1 Jun 2009 11:50:09 +0100 Borja Tarraso Hueso <borja.tarraso.hueso@googlemail.com> wrote: 

BTH> Yes, i understand that not everything uses the default prefix, but using
BTH> "C-10 n" does not work as I expected (read next emails or read the 10th
BTH> email) just always read next email. Also I understand that's not a bug if
BTH> the implementation of that does not take care about that, although i think
BTH> it could be good to do that as the rest of commands (in the same family -
BTH> "C-u #", etc) takes care of that.

I'm not sure why you would ever need to read the next N messages.  You
could define a keyboard macro I guess, but I don't see any utility in
providing that to all Gnus users.  Can you explain what you're trying to
do?

If the goal is to mark N messages as read, there's a command for that
and it takes the prefix argument.

Ted

Re: Possible gnus bug when pressed 'C-u n'

[Borja Tarraso Hueso]

[-- Attachment #1.1: Type: text/plain, Size: 1302 bytes --]

Hi Ted,

I was thinking in marking next 10 messages (or 4 if other prefix is used
like C-u n, etc) with (R)ead flag. As 'n' is marking the next one as (R)ead.

Thanks!

Borja Tarraso

2009/7/8 Ted Zlatanov <tzz@lifelogs.com>

> On Mon, 1 Jun 2009 11:50:09 +0100 Borja Tarraso Hueso <
> borja.tarraso.hueso@googlemail.com> wrote:
>
> BTH> Yes, i understand that not everything uses the default prefix, but
> using
> BTH> "C-10 n" does not work as I expected (read next emails or read the
> 10th
> BTH> email) just always read next email. Also I understand that's not a bug
> if
> BTH> the implementation of that does not take care about that, although i
> think
> BTH> it could be good to do that as the rest of commands (in the same
> family -
> BTH> "C-u #", etc) takes care of that.
>
> I'm not sure why you would ever need to read the next N messages.  You
> could define a keyboard macro I guess, but I don't see any utility in
> providing that to all Gnus users.  Can you explain what you're trying to
> do?
>
> If the goal is to mark N messages as read, there's a command for that
> and it takes the prefix argument.
>
> Ted
> _______________________________________________
> info-gnus-english mailing list
> info-gnus-english@gnu.org
> http://lists.gnu.org/mailman/listinfo/info-gnus-english
>

[-- Attachment #1.2: Type: text/html, Size: 1894 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Possible gnus bug when pressed 'C-u n'

[Ted Zlatanov]

On Tue, 14 Jul 2009 19:10:25 +0100 Borja Tarraso Hueso <borja.tarraso.hueso@googlemail.com> wrote: 

BTH> I was thinking in marking next 10 messages (or 4 if other prefix is used
BTH> like C-u n, etc) with (R)ead flag. As 'n' is marking the next one as (R)ead.

You can do that with the `d' key, e.g.

C-u 10 d

which is bound to the function gnus-summary-mark-as-read-forward.

Ted