headers
Harry Putnam | 1 Jun 2003 01:20
Favicon

Keeping a group visible.. dormant doesn't

I seem to recall being able to keep a group visible in Group buffer
simply by ticking something (?) dormant.  Then an asterisk appeared on
the left, and group remained visible thru thick and thin.  Now it
doesn't .... and that has been true for several version I think.  

It now takes a `u' tick to remain visible.  Is there some good reason
why dormant isn't sufficient?  With dormant it doesn't make anything
appear in summary unless one wants it too.

I think there is a var controlling this too.  Maybe I should just use
that.  Any one know what it is?
Permalink | Reply | 2 comments |
headers
Steinar Bang | 1 Jun 2003 01:23
Picon
Picon
Favicon

A RE: SV: AW: "collapser", anyone...?

Does anyone know if there is functionality to do RE: SV: AW:
etc. "collapsing" in the Subjects of articles?

I've looked through the washing and hiding stuff in articles sections
in the documentation without finding anything.

Nor does there seem to be a Subject simplify function to do this.
Permalink | Reply | 0 comments |
headers
Harry Putnam | 1 Jun 2003 01:21
Favicon

Re: Agent and 'Couldn't open server'

kai.grossjohann <at> gmx.net (Kai Großjohann) writes:

> Also, offline is for a single server, whereas plugged/unplugged is
> somewhat universal.

But only for agentized groups... or has that been changed?
Permalink | Reply | 1 comment |
headers
Robert Epprecht | 1 Jun 2003 11:07
Picon
Favicon

Re: Keeping a group visible.. dormant doesn't

Harry Putnam <reader <at> newsguy.com> writes:

> I seem to recall being able to keep a group visible in Group buffer
> simply by ticking something (?) dormant.  Then an asterisk appeared on
> the left, and group remained visible thru thick and thin.  Now it
> doesn't .... and that has been true for several version I think.  

I don't recall the described behaviour, but I would not like it anyway...
I think it's alright that if a group has only dormant and/or read messages
that it would *not* show up (by default) in the group buffer. YMMV.

Robert
Permalink | Reply | 0 comments |
headers
Sacha Chua | 1 Jun 2003 15:26
Picon
Picon

Re: Keeping a group visible.dormant doesn't

Harry Putnam <reader <at> newsguy.com> writes:

> I seem to recall being able to keep a group visible in Group buffer
> simply by ticking something (?) dormant.  Then an asterisk appeared on

If you want to keep a group visible, you can add (visible . t) to its
group parameters. From the *Group* buffer, type "G p". If the group
parameter is nil, replace it with ((visible . t)), else add (visible .
t) to the list.

That's probably not what you meant, but it might be useful. =)

--

-- 
Sacha Chua <sacha <at> free.net.ph> - Ateneo CS faculty geekette
interests: emacs, gnu/linux, wearables, teaching compsci
http://richip.dhs.org/~sachac/
Permalink | Reply | 0 comments |
headers
Eli Zaretskii | 1 Jun 2003 17:40
Picon

Re: MML charset tag regression

> From: Dave Love <d.love <at> dl.ac.uk>
> Date: Fri, 30 May 2003 10:23:21 +0100
> 
> "Eli Zaretskii" <eliz <at> elta.co.il> writes:
> 
> > The support for extended segments was implemented as an extension of
> > ctext to avoid a thorough rewrite of the ctext en/decoder.  As you
> > know, the ctext encoder and decoder are variants of the iso-2022
> > en/decoder and are handled by the same code (in C).
> 
> I don't see what this has to do with what I said.

It was intended to explain why the code was built on top of the
existing ctext en/decoder.  I'm sorry it wasn't helpful, but given the
attitude, perhaps I shouldn't be surprised.
Permalink | Reply | 0 comments |
headers
Kai Großjohann | 1 Jun 2003 18:31
Picon

Re: Agent and 'Couldn't open server'

Harry Putnam <reader <at> newsguy.com> writes:

> kai.grossjohann <at> gmx.net (Kai Großjohann) writes:
>
>> Also, offline is for a single server, whereas plugged/unplugged is
>> somewhat universal.
>
> But only for agentized groups... or has that been changed?

Only for agentized servers, that's right.

So plugged/unplugged applies to all agentized servers, whereas
offline applies to a single server only.  (Of course, more than one
server can be in offline state.)
--

-- 
This line is not blank.
Permalink | Reply | 0 comments |
headers
Steinar Bang | 1 Jun 2003 23:34
Picon
Picon
Favicon

Re: A RE: SV: AW: "collapser", anyone...?

>>>>> Maciej Matysiak <phoner.ding <at> blah.pl>:

> there is, if you add the stuff to message-subject-re-regexp
> variable.  default value covers only english version of reply
> prefix.

Hm... grep tells me that this variable is used in
gnus-simplify-subject-re in gnus-sum.el, and in
message-strip-subject-re in message.el.

As far as I can tell this means that the collapsing will work as
desired for summary buffers (ie. remove them all).

For messages being composed, this will remove them all, while I would
like a single Re: to be left there.  Or perhaps this is inserted
elswhere into the Subject of the message being composed?

But this regular expression isn't used by any article washing
function, so I would have to write something there.

> i'm all for expanding it with localized prefixes (polish 'odp', swedish 'sv',
> and so on). for the beginning:

> (setq message-subject-re-regexp
>  "^[
\t]*\\(\\(\\([Aa][Ww]\\)\\|\\([Oo][Dd][Pp]\\)\\|\\([Rr][Ee]\\)\\|\\([Ss][Vv]\\)\\|\\)\\(\\[[0-9]*\\]\\)*:[
\t]*\\)*[ \t]*")

> (i don't know any more translated re's).
(Continue reading)

Permalink | Reply | 2 comments |
headers
Steinar Bang | 1 Jun 2003 23:51
Picon
Picon
Favicon

Re: A RE: SV: AW: "collapser", anyone...?

>>>>> Steinar Bang <sb <at> dod.no>:

> As far as I can tell this means that the collapsing will work as
> desired for summary buffers (ie. remove them all).

Yes it did.  Excellent.

> For messages being composed, this will remove them all, while I would
> like a single Re: to be left there.  Or perhaps this is inserted
> elswhere into the Subject of the message being composed?

I ended up with a single "Re: ".  So obviously the latter.

> But this regular expression isn't used by any article washing
> function, so I would have to write something there.

That's still on, I guess.

But two out of three ain't bad. :-)

Thanx!

- Steinar
Permalink | Reply | 0 comments |
headers
Jesper Harder | 2 Jun 2003 04:20
X-Face
Picon

Re: one more bug in latest gnus

Vladimir Volovich <vvv <at> vsu.ru> writes:

> i saw some changes in CVS, and just synced to see if that fixed this
> bug. this bug is not yet fixed, i.e.
>
>   after pressing C-d on the first message in this thread, and
>   after doing reencoding with 0 g windows-1251 RET,
>   i see correctly re-encoded subject in the Article buffer:
>   Subject: Книга  Котельникова и Чеботаева
>   but in the Summary buffer, i see only "Книга"
>   but the rest of the subject is not shown.
>
> just to let you know so that will not get forgotten :)

This patch appears to fix it.  But I haven't checked carefully that it
doesn't break anything else.

*** /home/harder/gnus/lisp/gnus-sum.el	Sat May 17 18:14:30 2003
--- /home/harder/cvsgnus/lisp/gnus-sum.el	Mon Jun  2 04:18:16 2003
***************
*** 5713,5718 ****
--- 5713,5719 ----
        ;; Translate all TAB characters into SPACE characters.
        (subst-char-in-region (point-min) (point-max) ?\t ?  t)
        (subst-char-in-region (point-min) (point-max) ?\r ?  t)
+       (ietf-drums-unfold-fws)
        (gnus-run-hooks 'gnus-parse-headers-hook)
        (let ((case-fold-search t)
  	    in-reply-to header p lines chars)
(Continue reading)

Permalink | Reply | 0 comments |

Gmane