eichin@ATHENA.MIT.EDU ("Mark W. Eichin") (05/19/88)
One method I have seen (though it seems crude...) is to (setq rmail-mode-hook (function (lambda () (setq unread-command-char ?h)))) This will have the effect of sending an h as the next command executed; assuming normal bindings, this will get a summary buffer. This is probably appropriate in that the hooks are usually run before the buffer is set up, while the next command is executed after everything is done; maybe we need before hooks and after hooks... Or maybe this is grotesque enough that someone will be forced to post the right solution out of sheer revulsion. :-) _Mark_
jr@PEBBLES.BBN.COM (John Robinson) (05/20/88)
> One method I have seen (though it seems crude...) is to > Or maybe this is grotesque enough that someone will be forced to post > the right solution out of sheer revulsion. :-) Well, now that we are talking revolting and crude, there is always the route of adding to rmail.el the configuration defvar: (defvar rmail-start-in-summary-mode nil "If non nil, rmail will start up in summary mode.") together with the appropriate stuff in (rmail) or wherever. /jr jr@bbn.com or bbn!jr