On 5/3/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
On 5/2/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote:
> On 5/1/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > On 4/28/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> > > Does anyone actually use %+ and %- in bash, i.e. the last and next to
> > > last job to be used? 'fg' and 'bg' don't have to use %+, since running
> > > 'fg' or 'bg' with no arguments will do the same thing, and I find it
> > > easier to remember the job id of the current jobs than to remember
> > > what job was second last to be used. Therefore, I've seen very little
> > > reason to implement them, but I suppose different people might have
> > > different tastes.
> >
> > I'll take that as a no. Excellent. One less feature! :-D
> >
> Wait, I do ;-).
> I don't care whether it will be called %- or $job_order[1] or (jobs -o
> 1) but I do want a way to access the order in which jobs were last
> activated (launched or fg'd).
> In bash I have "alias gf 'fg %-'" which is very handy for alternating
> between 2 jobs; given the ordering of all jobs, it will be easy to
> implement more sophisticated switching...

I guess I agree.  It does make it easier to switch because you don't
have to think about which job you are switching to.  Also, if a couple
of jobs start with the same string, it is long to use the "fg
commandstring" pattern.  For example, you may heve to type
"fg vi\ /home/user1/project/file1"

You can use the job id in those cases, e.g. 'fg %1' will work just fine.


Perhaps it should be "fg -o 1" and "fg -o 2", which would be aliased
to "fg1" and "fg2".  This is not slower to type than "%-" because you
do not need to press the Shift key.


> Actually that's not what I really need.  Job control is a poor
> solution in today's windowed environments.  What would be really nice
> is for every suspended or backgrounded job to go to a new tab of the
> terminal.
> I'll check whether I can cook something up using 'dtach' and report back...

Nifty, but a solution to a different problem.  I think a shell should
be usable without a windowing enviromnent.

True, but I see nothing wrong with using additional functionality if
it is available, so long as things are perfectly useable without it.
Kind of liken how if you are running X, fish will use the X clipboard
to share the killbuffer between all fish instances and all other X
applications, but if you're not, an internal buffer is used instead.

--
Axel


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to