🚀 go-pugleaf

In article <1990Oct4.212140.11006@cbnewsu.att.com> mark@cbnewsu.att.com (Mark Horton) writes:
> > In patch #3 that will soon be available, you will be able to specify
> > the @-style format such as:
> >     dheller@cory.berkeley.edu
> > This is a "convenience" for the user -- it'll just internally use the
> > bang-formats discussed above.  I think bart and I are also planning
> > on supporting *user to imply the same thing as !user now...
> 
> This seems like a reasonable thing to do since user@host is the standard
> format that most people use these days.

But the bang-form is a superset of the @-format (in this context).
Anyway, as long as you can specify the @-format style, you needn't
really worry about the internal storage.

> > > When replying, if I forget to press "send" (or miss it) and then press
> > > "close", the reply window goes away and so does the reply button!
> > You can still hit the <compose> button,
> Yes, <compose> works, it just wasn't obvious that I should press it.
> You view <compose> as meaning "pop up the compose window", I view it
> as meaning "I want to send a new piece of mail".  I suspect users
> are more likely to make the latter interpretation.

If you can think of a better solution for this, I'm listening.
Keep in mind that real estate is a big issue/problem.  I don't
want to just "add another button"  -- we could change the label
on the <compose> button, for example, but to what?

> > >   In particular, when I'm paging through a long message and
> > > have a "more" at the bottom, I would like to be able to issue commands
> > > like "n" or "r" without having to "q" first.  I can do this in mushtool
> > > but not in curses mode.
> I seem to get mush's pager no matter what I ask for.
That's because (If I remember correctly) you are doing
    set PAGER=...
Just as in csh, you only use all-caps (customarily) for environment
variables.  You should have done
    setevn PAGER ...
note: no equal sign.  You can use this in your .mushrc or your .cshrc,
.login, or at the csh command line--mush honors your environment variables
(e.g., you can import mush configuration from your environment).
If you just want to use a pager specifically/only when using Mush:
    set pager = ...

> OK - I don't really want a separate pager, it takes too long to
> start up.
If you haven't been able to get it started, then how do you know?
It shouldn't take very long; it certainly doesn't take as long as
Mail takes to start up a new pager.

> I just want the built-in pager to do something reasonable
> (not just beep) when I type a mush command at it.  I realize this is
> hard to do if you use your own pager, but for the built-in one that
> I get anyway it should be easy.

We're looking at that now.

> > This is true, but vi is tuned to take full advantage of the capabilties
> > of the screen.  Mush just uses those curses(3X) commands that are most
> > portable across all versions of unix (that we've found).  We cannot do
> > reverse scrolling reliably (which would give you your desired effect)
> > and be assured that it works everywhere.
> 
> Are there bugs in screen scrolling on the BSD curses?  Or is it just slow
> to scroll backwards?  I think even the BSD curses will scroll the whole
> screen forward a line if you set scrollok to true.

curses doesn't have any reverse scrolling mechanisms in it.  It does
not do screen management very well at all when it comes to any kind of
screen scrolling.  For example, open a line above (like 'O' in vi)
is incredibly inefficient.  This is one reason why I hate emacs so much :-)

--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.