[Fish-users] Bug?: filename underlines
After correctly underlining a completed filename, Fish removes the underlining when the user types a space and some other character. Is this intentional? I think the underlining should stay unless the filename is modified to a string that is not the name of a file. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Multiline editing
Hurray for multiline editing! Is it possible to make it indent right after moving to the new line, rather than waiting for the first character to be typed? Then the cursor would not need to be moved again, unless the user types "end", which is unlikely. This will make it clearer to the user what's going on, and make Fish feel more stable. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Multiline editing
On 10/5/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > On 10/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Multiline editing rocks. Here are some thoughts. > > > > The ellipsis (…) at the start and end of lines is cool and makes clear > > that the line was wrapped. But it also complicates pasting commands > > into an editor, as you have to delete all the ellipses. Granted, > > pasting would require re-formatting anyway if a word or string is > > continued on a new line. But when indentation is implemented, wrapped > > words or strings should not be indented, only commands starting on the > > new line. > > I disagree. As you note, you have to edit the commands regardless of > the ellipsis to remove the additional line breaks. The ellipsis mean > that can quickly tell what line breaks should be removed, and if you > do a lot of pasting, you can define a command to remove all instances > of '\u2026\n *\u2026' to automate the task. > > Also, though I just noticed that ^K is currently broken (kills to end > of command, not end of line), using the fish clipboard integration > should be a much simpler way of copying and pasting between > applications. > > That said, I don't know how to best mix indentation and wrapping yet, > but I suspect that your suggestion is a good one, since it makes > clearer the distinction between line breaks and wrapped lines. > > > > > Also, ellipsis may make editing a little confusing, because it looks > > like an ordinary character, but actually you can't delete it. Would > > it be better without ellipses? If they stay, can they be color of > > comments or something? > > Yes, coloring them makes sense. Will do. > > > > > Perhaps it would be better to ignore multiple newlines, as they take > > too much space. For example, > > > > for x in 1 2 3 > > echo hello > > > > end > > > > Once entered, a command with an empty line takes terminal space every > > time you browse the history. And I don't think a need to use empty > > lines arises amlost ever. And if it really does, you can use a line > > with an empty comment instead. So the rationale is similar to that > > for disapplowing re-printing the prompt after an empty line. > > Fish allows you to have newlines insed quotes, for example the > following is perfectly valid fish code, though the multiline reader > doesn't know it yet (works in a script): > > printf " > GET foo.html HTTP/1.1 > some-server.com > > " | whatever [...] Rght. I was talking about things other than strings. Fish knows a string when it sees one. > Also, if the user entered a command with an empty line, s/he probably > had some reason for doing it (Possibly to group the code into logical > segments, or to create nice ASCII art to beautify the history browsing > experience, both of which are valid use cases), and hence the computer > should not second guess the user. In my experience, the reason is usually a nervous twitch. As with the empty command line, people have a habit of hitting Enter while composing. They don't think about the fact that their history would be more usable without it, but it would be. To say that the user should always have control is to reject auto-indentation in editors, Other times it's a slip of the hand. So users have to be careful not to hit the key. If Enter can only make one consecutive newline (outside strings), the system will feel more stable (less fragile). ASCII art works with comments. We are trying to make a shell that is easy to use for normal use. > > (Unfortunately, Axel must not have liked this feature because he did > > away with it; I really liked it.) > > I liked it too, though not passionately. There was a long discussion > (should be in the mailing list archives) and most people felt the > other way. I'm way to keen on listening to other people to be a good > dictator. :( With me it was fiery love that burned. I can do the dictating on your behalf, if that would help... - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Multiline editing
On 10/6/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > On 10/6/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote: [...] > > Not necessarily. The terminal stores a hidden bit at every end of > > line, rememebering whether it was crossed by wrapping a long text. > > I'm not sure what's the exact rule that controls it but if you echo a > > long string that wraps and cut-and-paste it you will get the long text > > back without newlines. > > Any information on how to manipulate the terminals line wrapping would > be greatly appreciated. Are you saying that you do not know how to make the text appear at column 1 on the new line? That's why it has to be indented at least as much as the prompt? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Slightly altered format for fish history file
On 10/8/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: [...] > Currently, a backslash followed by a newline is interpreted as a > newline in fish. This means that you can write e.g. > > pwd\ > pwd > > and it will execute the 'pwd' command twice. > > However, this is not true in a quoted environment. Writing > > echo "hello\ > goodbye" > > Will output > > hello\ > goodbye > > and not > > hello > goodye > > I'm proposing we change this, in order to make it possible to save a > multiline command in the history by backslash escaping all newlines. This does not sound appealing from the point of view of syntax simplicity. Having to escape backslashes gets complicated. Inside quites at least, text should be taken at face value as much as posible. This is violated with the $-construct, but there should be as few exceptions as possible. How abot this. Write a comment with a time stamp before each command, that begins with a signature like "fish command executed at " or something like that. It would be easily parsable and documented. Then perhaps the backslash escapes can be avoided. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Slightly altered format for fish history file
On 10/8/06, Martin Bähr <[EMAIL PROTECTED]> wrote: > On Sat, Oct 07, 2006 at 10:45:13PM +0200, Axel Liljencrantz wrote: > > the fish syntax needs > > to be changed so that a backslash before a newline is ignored even > > when inside quotes, which is not the case today. > > what does that mean? Currently, a backslash followed by a newline is interpreted as a newline in fish. This means that you can write e.g. pwd\ pwd and it will execute the 'pwd' command twice. However, this is not true in a quoted environment. Writing echo "hello\ goodbye" Will output hello\ goodbye and not hello goodye I'm proposing we change this, in order to make it possible to save a multiline command in the history by backslash escaping all newlines. > > > Once the history problem is fixed, the new config file reshuffle is > > done, and ^K and various other keyboard shortcuts are made to operate > > on a single line and not the entire buffer, all known fish regressions > > should be fixed, and one can start thinking about a new fish release. > > as in 1.21.13 or 1.22? I definitely think the next release should be 1.22.0. Multiline editing and the proposed new file layout are big enough features to warrant the version bump. > > > Also, I have added support for autoindentation to fish. Looks cool. :-) > > can't wait to see that :-) > > 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 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
Re: [Fish-users] Slightly altered format for fish history file
On Sat, Oct 07, 2006 at 10:45:13PM +0200, Axel Liljencrantz wrote: > the fish syntax needs > to be changed so that a backslash before a newline is ignored even > when inside quotes, which is not the case today. what does that mean? > Once the history problem is fixed, the new config file reshuffle is > done, and ^K and various other keyboard shortcuts are made to operate > on a single line and not the entire buffer, all known fish regressions > should be fixed, and one can start thinking about a new fish release. as in 1.21.13 or 1.22? > Also, I have added support for autoindentation to fish. Looks cool. :-) can't wait to see that :-) 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/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
