Re: [Fish-users] less wishlist items

2006-10-30 Thread Axel Liljencrantz
On 10/29/06, Martin Bähr [EMAIL PROTECTED] wrote:
 hi,

 i was just going through the wishlist and i noticed that there are
 items that can actually be removed since they have been implemented.
 (how nice is that? :-)

:)


 that said, there is one item, that i think would make sense for the 1.22
 release since it changes the behaviour, namely:
   * Per process output redirection

Honestly, at this point I really only want to release 1.22.0. No more
major features. Except for the new history implementation, which I
wanted to get in in order to avoid having two separate syntax changes
to the history file format, all patches that have gone in for the last
few weeks have been either bugfixes, cleanups or minor features that
can more or less be grafted on top of the existing code. The ** change
was somthing like 4 lines of code, for example. I have no problems
with releasing 1.23.0 in a few weeks with minor incompatibilities.


 also, the multiline editing is very nice, but it would be even nicer if
 the up/down arrow keys could be used to navigate within the lines.
 so basicly, they would walk the history line by line and not command by
 command. it would slow down a quick browsing of the history a bit, but
 it would add a lot of convenience for editing multiline commands...

Not sure that's a good idea. For example, when you are searching the
history, if you come across a multiline entry, you will be stuck. And
modality is bad. There might be some reasonable solution to this, but
I don't see one at once.


 (after an intensive conference and a move to a new home without
 internet, i am slowly getting back to normal, and finding some time to
 actually appreciate the new features in fish. great work!)

 greetings, martin.
 --
 cooperative communication with sTeam  - caudium, pike, roxen and unix
 offering: programming, training and administration   -  anywhere in the world
 --
 pike programmer   travelling and working in europe open-steam.org
 unix system-  bahai.or.atiaeste.(tuwien.ac|or).at
 administrator (caudium|gotpike).org  is.schon.org
 Martin Bähr   http://www.iaeste.or.at/~mbaehr/


-- 
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=lnkkid=120709bid=263057dat=121642
___
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users


Re: [Fish-users] less wishlist items

2006-10-30 Thread Martin Bähr
On Mon, Oct 30, 2006 at 04:44:45PM +0100, Axel Liljencrantz wrote:
 Not sure that's a good idea. For example, when you are searching the
 history, if you come across a multiline entry, you will be stuck.

not really.
you only have to hit the arrow a few more times to get to the next
entry.
the current way is verry annoying, it makes me lose work, because i keep
forgetting that i can not switch lines in multiline mode.
i start writing, then i want to go back a line, and then oops, and my
half written command is gone. bad.

it would not be so bad if the half written command did not get lost.

and maybe instead of the arrow keys some other keys can be provided to
switch lines.

in that same area: ctrl-a and ctrl-e should only move within one line.
and essentially, all the editing features of a single line command
should be available within a line of a multiline command.

just today i wanted to build a look and within it reuse a command that i
had used before. being able to activate a search at that point would
have been ideal.

and, while i am at it: enter should not execute the command unless you
are at the end. otherwise it is not possible to add more lines to an old
command without first going to the end, to remove something to make sure
the command is incomplete, because the enter will run the command if it
is complete.

all arguments about modality aside: 
multiline editing already IS a different mode.

greetings, martin.
-- 
cooperative communication with sTeam  - caudium, pike, roxen and unix
offering: programming, training and administration   -  anywhere in the world
--
pike programmer   travelling and working in europe open-steam.org
unix system-  bahai.or.atiaeste.(tuwien.ac|or).at
administrator (caudium|gotpike).org  is.schon.org
Martin Bähr   http://www.iaeste.or.at/~mbaehr/

-
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=lnkkid=120709bid=263057dat=121642
___
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users


Re: [Fish-users] less wishlist items

2006-10-30 Thread Axel Liljencrantz
On 10/30/06, Philip Ganchev [EMAIL PROTECTED] wrote:
 On 10/30/06, Martin Bähr [EMAIL PROTECTED] wrote:
  On Mon, Oct 30, 2006 at 04:44:45PM +0100, Axel Liljencrantz wrote:
   Not sure that's a good idea. For example, when you are searching the
   history, if you come across a multiline entry, you will be stuck.
 
  not really.
  you only have to hit the arrow a few more times to get to the next
  entry.

 I have used it on other systems, (Matlab?) and it is very annoying.
 To bring up a 6-line command that was executed 5 commands ago, you
 have to press the arrow 30 times, and either count or scrutinize every
 time whether this is the line you want.

Yep, Matlab makes reexecuting a multiline command a real chore. The
only conclusion that I can draw from this is that you sometimes want
to access the history on a line-by-line basis and sometimes on a block
basis. And no matter which one you pick, the grass will always be
greener on the other side.

One possibility is to use some special keyboard sequence to give you
an extra prompt. From this 'extra prompt' you can then search the
history and copy the right parts of it to the killring. Then you exit
the secondary prompt and yank the result into the primary prompts
command buffer.

[...]
  and maybe instead of the arrow keys some other keys can be provided to
  switch lines.

 You mean move to the next or previous line within the same command?
 Control+UpArrow and +DownArrow would parallel Control+LeftArrow and
 +RightArrow which by default move by one word.  But we are approaching
 the state of too many key combinations to remember, so we should unify
 functionality whenever possible.

Unification in this context implies modality though. Damned if you do,
damned if you dont. Though I kind of like overloading lots and lots of
things on the arrow keys. I don't know why, I just do.


 You can make UpArrow move the cursor to the previous line of the
 command unless it is already at the first line,  in which case search
 the history.  But then you might have to hit UpArrow many times to
 search; and you would have to pay attention to what mode (line) you
 are on when editing.

Doesn't sound very cool to me.

[...]

  just today i wanted to build a look and within it reuse a command that i
  had used before. being able to activate a search at that point would
  have been ideal.

 I am working on a proposal that may let you do that without having to
 explicitly search.

Looking forward to hearing it.


  and, while i am at it: enter should not execute the command unless you
  are at the end. otherwise it is not possible to add more lines to an old
  command without first going to the end, to remove something to make sure
  the command is incomplete, because the enter will run the command if it
  is complete.

 I think you mean Enter should not execute the command unless the
 cursor is at the end of the command.  Maybe so, not sure.  The
 tradeoff is obvious -- it makes it harder to actually execute the
 command, which is a much more common operation than indenting.  You
 can move the cursor to where you want to indent, cut the line and
 press Enter then.

 I would prefer if the user did not have to worry about indentation.
 If the command gets too long to fit on one line, Fish should indent it
 automatically.  A Pascal editor for the Mac which I used about 10
 years ago worked like that.  It was wonderful!  You did not have to
 worry about formatting, only about the content.  But I know some
 people who have never tried it will complain on religious grounds.

I use auto-newlines in C, and I love it. Semicolons and brackets
automatically insert newlines at the right places. This might make
sense for fish too.

[...]

-- 
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=lnkkid=120709bid=263057dat=121642
___
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users