headers
Lars Magne Ingebrigtsen | 1 Feb 1996 01:35
Picon
Picon
Picon

Re: gnus-summary-limit-to-unread

abraham <at> dina.kvl.dk (Per Abrahamsen) writes:

> When I press `x', articles marked with `Q' aren't removed as I would
> have expected. 

Yup.  Fix in September Gnus v0.33.

> I'd also like to be able to remove all unread articles, except those
> needed to connect loose threads.

I've added this to the Red Gnus todo list.

--

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."
Permalink | Reply | 0 comments |
headers
Lars Magne Ingebrigtsen | 1 Feb 1996 01:35
Picon
Picon
Picon

Re: Topics: Two comments

abraham <at> dina.kvl.dk (Per Abrahamsen) writes:

> A one-line *Group* buffer doesn't seem very useful to me.

It says how many unread articles there are in all the topics.  Which
is information that would be otherwise unavailable if not for the
root topic.  And I just like being able to fold away everything, but
that may just be me.

--

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."
Permalink | Reply | 2 comments |
headers
Jason L Tibbitts III | 1 Feb 1996 04:42
Picon
Favicon

Can the tree show the _whole_ thread?

My belief is that the summary buffer should show a good bit of info about
the articles of interest, the tree buffer shows the big picture with less
detail, and the article buffer shows everything about just one message. So
I sort of expected the tree display to show the entire thread, including
old articles and sparse nodes and everything.  I tried playing with
gnus-fetch-old-headers and gnus-make-sparse-threads and can get old and
sparse articles to show up in the summary buffer but the tree buffer shows
only the new articles and whatever sparse nodes are required to connect
them (as it always does).

What I'm really trying to get is a summary buffer with no extraneous
information (no O or Q lines) but a tree buffer with a picture of
everything back to the root article, preferably with old articles shown
like sparse articles, but with useful info instead of ***.  For example,

I get this:               I want this:

{***}                     (***)            
  |--\-----\		    |--\-----\     
[Ste] [Mar] [Per]	  (Bla) (***) (Ste)
               		    |     |     |  
                   	  (Mar) (Urk) [Per]
   			    |     |        
     			  (Joe) [Ste]      
			    |              
                	  [Mar]            

And a summary buffer that just looks like:

  +[ 106: Steven L. Baur      ] Re: Gnus5, procmail, and reading mail
(Continue reading)

Permalink | Reply | 1 comment |
headers
Samuel Tardieu | 1 Feb 1996 14:32
Picon
Picon

Re: Two NNTP servers in different modes

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi <at> ifi.uio.no> writes:

Lars> Samuel Tardieu <sam <at> inf.enst.fr> writes:

>> I would want to set "news.ext.jussieu.fr" (the good one) as my
>> default NNTP server *but* I want the news I post to go through
>> "news.enst.fr" (the slow one). To make this story short, I want to
>> read my news from a server and post on another one.
>> 
>> Is there a simple way of setting things like this with September
>> Gnus ?

Lars> Just set `gnus-post-method' to an nntp method pointing to
Lars> "news.enst.fr".

Hmmm... This works when posting from within a group, not when pressing
`a' in the *Group* buffer (gnus-newsgroup-name seems to be nil so
gnus-post-method is called with nil as group name and it returns
gnus-select-method, even if gnus-post-method is set).

Maybe the (cond ...) in gnus-msg.el (gnus-post-method) should have:

  ((null group-method) (or gnus-post-method gnus-select-method))

instead of

  ((null group-method) gnus-select-method)

?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Aharon (Al) Schkolnik | 1 Feb 1996 15:58
Picon

Is there a problem with this list ?


	Sorry to bother everyone, but I've already sent a message to
ding-request, and have received no response. Also, I have not received
anything from the list for a few days. 

Is everything O.K. out there ?

--
  The day is short, and the work is great,     |   Aharon Schkolnik
  and the laborers are lazy, and the reward    |   Aharon <at> Matat.Health.Gov.IL
  is great, and the Master of the house is     |
  impatient. - Ethics Of The Fathers Ch. 2     |
Permalink | Reply | 0 comments |
headers
Jack Vinson | 1 Feb 1996 17:07
Picon

gnus-summary-tick-article-forward


I've noticed before that function fetches the article in question.  Is this
necessary?  It is most noticeable for large articles, since I've got
highlighting turned on.  

--

-- 
Jack Vinson                       jvinson <at> cheux.ecs.umass.edu
"I wish I were spatial, but I'm a plane." - Radiohead (sorta)
Permalink | Reply | 2 comments |
headers
Hallvard B Furuseth | 1 Feb 1996 18:03
Picon
Picon
Favicon

Re: September Gnus 0.30 is released

> (Whew!  Yet Another Gnus Variable avoided.  I'm getting better at
> that, I think.  :-)

I think that one is called gnus-novice-user anyway.

Regards,

Hallvard
Permalink | Reply | 0 comments |
headers
Wes Hardaker | 1 Feb 1996 17:35
X-Face
Picon
Picon

Re: Topics: Two comments


>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi <at> ifi.uio.no> writes:

    abraham <at> dina.kvl.dk (Per Abrahamsen) writes:
    Per> A one-line *Group* buffer doesn't seem very useful to me.

    Lars> It says how many unread articles there are in all the
    Lars> topics.  Which is information that would be otherwise
    Lars> unavailable if not for the root topic.  And I just like
    Lars> being able to fold away everything, but that may just be me.

I have to agree here...  What DO you want a one line group buffer for?
I mean, WHY do you fold that top group?  What does it give you (other
than a mostly blank screen)?  

Just Curious,
Wes
Permalink | Reply | 1 comment |
headers
Jens Lautenbacher | 1 Feb 1996 17:06
Picon
Picon

Re: Topics: Two comments

>>>>> "PA" == Per Abrahamsen <abraham <at> dina.kvl.dk> writes:

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi <at> ifi.uio.no> writes:
    LMI> It was much easier to write the code using a single root. 
	[...]
    PA> A one-line *Group* buffer doesn't seem very useful to me.

    LMI> The people who don't like it can just rename it to "".

    PA> ----------------------------------------
    PA> [  -- 6 ]
    PA>   [ Emacs -- 4 ]
    PA>       2: nnml:ding.list            Mail to the Gnus list
	[...]

    PA> What I would like is:

    PA> ----------------------------------------
    PA> [ Emacs -- 4 ]
    PA>     2: nnml:ding.list            Mail to the Gnus list
	[...]
    PA> Maybe by setting a
    PA> `gnus-group-hide-top-level-topic-and-don't-indent-second-level-topics'
    PA> variable?

I _strongly_ second that. There should also be a variable which would
tell GNUS where to add groups not belonging to any topic yet. 
So newly subscribed groups would always added e.g. to `Misc'. 

Maybe one could go a little further and provide for the possibility
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hallvard B Furuseth | 1 Feb 1996 17:58
Picon
Picon
Favicon

Re: filepermissons

> Some people are very secretive, though.  There should be
> a way to specify the file permissions of the auto-saved dribble file.
> One does not want people to know that one is reading
> "comp.language.c++".  :-)

Right.  So why not just let the default mode for files and directories
that gnus by default creates in $HOME, be 0600.  If you can infer a
better mode from ~/.newsrc or whatever, fine.  But while people can and
do complain about lack of privacy, I don't really expect anyone to
complain because their dribble file isn't public.

Regards,

Hallvard
Permalink | Reply | 0 comments |

Gmane