Simple feature beg

Simple feature beg

[Jason L Tibbitts III]

There are two things I miss from Mew, the mail reader I used to use:

1. it would learn its concept of filing rules after you filed a message
   once.  (Mew's filing is like 'B m'.)  It did this simply based on the
   From: header, but it was still quite useful.  I don't want to set up
   filing rules foe every possible piece of mail.  It also supplied a
   useful default generated from the user-id in the From: line, so this
   message would file into 'tibbs' by default.

2. I would kill for a little something that let me pop into a folder, read
   some mail, and quit not back to the Group buffer but to whatever buffer
   configuration I had before I popped in.  This would make it so much
   simpler to read a new incoming message without having to screw up my
   buffer history.

 - J<

Re: Simple feature beg

[Lars Magne Ingebrigtsen]

Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:

> 1. it would learn its concept of filing rules after you filed a message
>    once.  (Mew's filing is like 'B m'.)  It did this simply based on the
>    From: header, but it was still quite useful.  I don't want to set up
>    filing rules foe every possible piece of mail.  It also supplied a
>    useful default generated from the user-id in the From: line, so this
>    message would file into 'tibbs' by default.

This is certainly doable, but these new split rules would have to be
stored somewhere.  And I think a new split variable would have to be
added, which makes things more complicated than they already are, so I
don't know if it's worth it...

> 2. I would kill for a little something that let me pop into a folder, read
>    some mail, and quit not back to the Group buffer but to whatever buffer
>    configuration I had before I popped in.  This would make it so much
>    simpler to read a new incoming message without having to screw up my
>    buffer history.

I always have two Emacs frames up -- one with Gnus in, and one with
everything else in.  I have

(global-set-key "\C-co" 'other-frame)

which is nice, since `C-x o' is `other-buffer'.

After starting to do this, things are much tidier.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Simple feature beg

[Jason L Tibbitts III]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> I always have two Emacs frames up -- one with Gnus in, and one with
LMI> everything else in.  I have

And I always use text mode, since most of my real work is done over a modem
line.  I would probably spend some time to figure out how
save-window-excursion works, but I'm not sure how to wait until the uses
exits the group before restoring it.

 - J<

Re: Simple feature beg

[Per Abrahamsen]

Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:

> And I always use text mode, since most of my real work is done over a modem
> line.  

You can have multiple frames in text mode too.

Re: Simple feature beg

[Jason L Tibbitts III]

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

PA> You can have multiple frames in text mode too.

Well I'll be damned.

 - J<

Re: Simple feature beg

[Mark Eichin]

> PA> You can have multiple frames in text mode too.
> Well I'll be damned.

Yeah, probably :-) Have you tried it? multiple frames on a tty is
unpleasant at best, the ordering isn't consistent (or at least I don't
have a good model for it) and I've seen no way of naming frames... On
the other hand, I've used "wicos" (WIndow COnfigurations, used to be
called screens):
;; LCD Archive Entry:
;; wicos|Heikki Suopanki|suopanki@phoenix.oulu.fi|
;; Save and restore multiple window configurations within Emacs.|
;; 92-04-07|1.3|~/misc/wicos.el.Z|  

for *years* and it gives a nice model for handling this.  One wico has
gnus, one has some interactive messaging stuff, then others simply
have different projects.

Re: Simple feature beg

[Kai Grossjohann]

Off-topic alert!

>>>>> Mark Eichin writes:

  Mark> ;; LCD Archive Entry:
  Mark> ;; wicos|Heikki Suopanki|suopanki@phoenix.oulu.fi|
  Mark> ;; Save and restore multiple window configurations within Emacs.|
  Mark> ;; 92-04-07|1.3|~/misc/wicos.el.Z|  

I've been using it when I used Emacs 18.  Is there a way to make it do
something sensible with frames?  In that switching to a new frame
means switching to a new wico, too?

kai
-- 
A large number of young women don't trust men with beards.
(BFBS Radio)

Re: Simple feature beg

[Hrvoje Niksic]

Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:

> >>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> LMI> I always have two Emacs frames up -- one with Gnus in, and one
> LMI> with everything else in.  I have
> 
> And I always use text mode, since most of my real work is done over
> a modem line.  I would probably spend some time to figure out how
> save-window-excursion works, but I'm not sure how to wait until the
> uses exits the group before restoring it.

What does `save-window-excursion' have to do with it?  Unless I am
missing something, GNU Emacs is capable of having more than one frame,
even in tty mode.  E.g. `C-x 5 2', `C-x 5 o' and others work as
expected.  I guess one can call it a fancy way of keeping multiple
window configurations around, but it's very intuitive to me.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
* Q: What is an experienced Emacs user?
* A: A person who wishes that the terminal had pedals.

Re: Simple feature beg

[David Moore]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
> 
> > 1. it would learn its concept of filing rules after you filed a message
> >    once.  (Mew's filing is like 'B m'.)  It did this simply based on the
> >    From: header, but it was still quite useful.  I don't want to set up
> >    filing rules foe every possible piece of mail.  It also supplied a
> >    useful default generated from the user-id in the From: line, so this
> >    message would file into 'tibbs' by default.
> 
> This is certainly doable, but these new split rules would have to be
> stored somewhere.  And I think a new split variable would have to be
> added, which makes things more complicated than they already are, so I
> don't know if it's worth it...

Might be able to leverage on custom to store them somehow.  Also, I
don't think you'd want a new variable.  Well, it would be a new
variable, but not directly parsed by gnus for splitting.  Probably
better to let the user splice those rules into their own split rules at
an appropriate place.



-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | In a cloud bones of steel.

Re: Simple feature beg

[Per Abrahamsen]

I think we need a new split function.

Re: Simple feature beg

[Lars Magne Ingebrigtsen]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I think we need a new split function.

Some sort of `nnmail-split-by-move-rules' or something?  Yes -- I
don't quite see how to fit the `B m'-induced split rules into the
fancy splitting scheme, for instance.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Simple feature beg

[Paul Franklin]

>>>>> Per Abrahamsen writes:

 > I think we need a new split function.

nnmail-split-adaptive?

:)

--Paul

Re: Simple feature beg

[Kai Grossjohann]

  Jason> 2. I would kill for a little something that let me pop into a
  Jason> folder, read some mail, and quit not back to the Group buffer
  Jason> but to whatever buffer configuration I had before I popped
  Jason> in.  This would make it so much simpler to read a new
  Jason> incoming message without having to screw up my buffer
  Jason> history.

  Lars> I always have two Emacs frames up -- one with Gnus in, and one
  Lars> with everything else in.

I also have this, but it *still* messes up the buffer list :-(

Try doing something in your Gnus frame then do C-x b in some other
frame -- you sometimes (always?) get a Gnus buffer offered.  At least
if I'm not mistaken.

The problem seems to be that all frames share the same buffer list, so
switching to a buffer in one frame moves the buffer to the top of the
buffer list in all frames.

kai
-- 
A large number of young women don't trust men with beards.
(BFBS Radio)

Re: Simple feature beg

[Hrvoje Niksic]

Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:

> I also have this, but it *still* messes up the buffer list :-(
> 
> Try doing something in your Gnus frame then do C-x b in some other
> frame -- you sometimes (always?) get a Gnus buffer offered.  At least
> if I'm not mistaken.

A cure to this is to exit Gnus with `z' and re-enter it with
`M-x gnus' (I bind it to `C-c g').  Works like a charm, as `z' kills
off all the buffers instead of Group buffer, and buries the Group

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Good pings come in small packets.

Re: Simple feature beg

[Kai Grossjohann]

>>>>> Hrvoje Niksic writes:

>>>>> Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:

  Kai> Try doing something in your Gnus frame then do C-x b in some
  Kai> other frame -- you sometimes (always?) get a Gnus buffer
  Kai> offered.  At least if I'm not mistaken.

  Hrv> A cure to this is to exit Gnus with `z' and re-enter it with
  Hrv> `M-x gnus' (I bind it to `C-c g').  Works like a charm, as `z'
  Hrv> kills off all the buffers instead of Group buffer, and buries
  Hrv> the Group

This solves the Gnus problem but not the more general problem -- I use
multiple frames for other things, too.

Thanks for your hint,
kai
-- 
A large number of young women don't trust men with beards.
(BFBS Radio)

Re: Simple feature beg

[sjm]

I'm afraid this question might have been asked (and answered) while I wasn't
listening. The listserver for this list seems to have changed, at least the
from address. This of course confused my filter (procmail.) I also notice that
reply on my mailer now gives the address of the sender. I thought the from
line used to be the address of the list.

Anyway, what does anyone recommend as the correct filter pattern to match this
list?

If this has been asked please reply directly to me so that my clutter doesn't
get multiplied.


Thanks,

Steve Morris
sjm@judgement.com

Re: Simple feature beg

[Justin Sheehy]

sjm <smorris@xionics.com> writes:

> reply on my mailer now gives the address of the sender. I thought the from
> line used to be the address of the list.

This is correct behavior.  Reply should (in the absence of a Reply-To:
header) send mail to the originator of a message.  'followup' or 'wide
reply' or somesuch thing should go to the list.

Of course, if you are using Gnus, all of this quickly becomes intuitive.

> Anyway, what does anyone recommend as the correct filter pattern to
> match this list?

Matching on 'ding' in the 'To: ' or 'Cc: ' headers has always worked
fine for me.

-Justin