Mutt + Screen + Vim question

2000-11-03 Thread Steve Bankowitz

I currently use something along the lines (in my $HOME/.muttrc)

  set editor="vim '+/^$'"

(pretty standard stuff.)  But every once and a while I would like to
jump back to Mutt to check a message.  Since I'm running screen I
thought, ``Oh, I'll just spawn vim off in another screen and then jump
back to mutt if need be.''

Well if I do just that:

  set editor="screen vim -f '+/^$'"

Screen spawns off a vim session just fine, but the contents of the file
is empty.  I used the `-f` thinking that vim was detaching from the
shell, but know difference is noticed.

So my next try was to write a quick wrapper around screen and vim and
pass it argv1.

  % cat hack 
  #!/bin/sh
  /usr/apps/bin/screen /usr/apps/bin/vim -- $1

And in my .muttrc file.

  set editor="/home/sbank/hack"

Still no go.  Screen spawns with vim, but no e-mail message to edit.

Does anyone have any suggestions?  (I looked in the mail archives, but
all I came up with is someone saying you should try the `-x` option to
vim.  Which is clearly wrong if you just do a quick man on vim.)

Thanks,
Steve



Re: Mutt + Screen + Vim question

2000-11-03 Thread Steve Bankowitz

Brian D. Winters [[EMAIL PROTECTED]] wrote:
 On Fri, Nov 03, 2000 at 03:19:30PM -0500, Steve Bankowitz wrote:
  (pretty standard stuff.)  But every once and a while I would like to
  jump back to Mutt to check a message.  Since I'm running screen I
  thought, ``Oh, I'll just spawn vim off in another screen and then jump
  back to mutt if need be.''
 
 Why not leave your editor stuff alone, and spawn another mutt in
 another screen?

How would I do that?  Would I write a macro for `m`?

  macro index m |screen mutt  %s

Or something along those lines?



Re: [OT] Re: Mutt + Screen + Vim question

2000-11-04 Thread Steve Bankowitz

Kai Blin [[EMAIL PROTECTED]] wrote:

 * Conor Daly [EMAIL PROTECTED] [04/11/00, 12:52:53]:

  What's the advantage of using screen over the ALTF1 - ALTF6
  consoles?  Can screen be used remotely or something?

 Yes, you can detach the session and logout / login from another
 console and retach the session... I'm using this for my IRC client,
 not for mutt, though

And more importantly I'm on a Solaris box! :-) No virtual consoles here.



Re: IMAP blues

2000-11-08 Thread Steve Bankowitz

JT Williams [[EMAIL PROTECTED]] wrote:
  -:  set envelope_from
  
  Ok, that did the trick.  Thanks!
  
 Well, maybe I spoke too soon.
 
 It's true that the list servers I was having problems with are
 now recognizing me, but our SysAdmin tells me there are still
 problems (see his explanation below).  Is this really a problem?
 I'd like to keep using mutt/IMAP if I could  TIA/jtw
 ---
MUTT seems to use normal sendmail channels to send messages rather
than connecting directly to the IMAP server.  We run in a full IMAP
environment (/var/mail is not mounted to client machines and clients
do not run sendmail daemon).  
 
This results in the sender's address being set to user@localhost
regardless of what MUTT settings are changed.  The final header 
shows the sender's address as being from the workstation MUTT was 
running on rather than the mail server.  In this respect, it behaves 
exactly like "mailx".

It looks like you use Sun's sendmail.  So here's what I would do
to fix your problem.  (If this isn't Sun's Sendmail then check out
sendmail.org, but the process is almost esactly the same.)

  # /usr/lib/mail/cf
  # cp imain-v7sun.mc darwin.mc
  # vi darwin.mc   (or use your favorite editor)

add the following lines above the FEATURE lines.

  MASQUERADE_AS(darwin.sfbr.org)
  MASQUERADE_DOMAIN(darwin.sfbr.org)
  FEATURE(masquerade_entire_domain)
  FEATURE(masquerade_envelope)

add this line after the FEATURES lines.

  define(`SMART_HOST', `mailhost.$m')

and change `mailhost.$m` to the fully qualified name of your IMAP
server.  Once that is done, save dawin.mc and use m4 to redo the
sendmail.cf file.

  # pwd
  /usr/lib/mail/cf
  # /usr/ccs/bin/m4 ../m4/cf.m4 darwin.mc  darwin.cf

then try darwin.cf, if all is well copy it over to /etc/mail as
sendmail.cf.