RE: [RP] Re: what about... (features)

[Casey Allen Shobe]

For what it's worth, I really hope neither of these get used.  It is after
all a simple command prompt.  I certainly don't want to have the overhead of
emacs nor do I want to have it anywhere near my system, and I don't see why
a nice light window manager has to become dependant on xterm either.  I'd
rather not have a constantly-running xterm that I'm not really using for
such a simple purpose.

PostgreSQL has an --enable-readline option, and when you use it, you get a
nice .psql_history in your home directory, tab completion, etc. etc.  I
think the best thing would be to have internal optional readline support.
Plus, a .ratpoison_history would be nifty :).

- Casey

> -----Original Message-----
> From: twb [mailto:address@hidden
> Sent: 1. maí 2003 07:06
> To: address@hidden
> Subject: [RP] Re: what about... (features)
> 
> 
> Quoth Michael Livshin <address@hidden>
> >  while folks are thinking in this direction, how about writing a
> >  simple (in theory, at least) Emacs <-> ratpoison glue, so 
> that you'd
> >  have a dedicated Emacs instance running all the time, unmapped, and
> >  pop up a special minibuffer-only (or not) frame for RP 
> command input.
> > 
> >  pluses:
> > 
> >  . no need to spawn a whole new xterm process for each command
> 
> You can do this with an xterm, too.  
>   1) Call an RP-input (C-t !).  This makes a new xterm and maps it.
>   2) The next time a newline is pressed, pass it on to xterm 
> and unmap it.
>   3) Next time C-t ! is pressed, map the xterm again.
> 
> You still have to (un)map it, but it's not a whole new process.
> 
> -twb
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Ratpoison-devel mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/ratpoison-devel
>