On Fri, Nov 03, 2006 at 05:49:50PM -0500, Philip Ganchev wrote:
Shift+PageUp = scroll the output up one screen (in common
please do not use keycombinations involving pgup/pgdown or or related,
as they do not exist as seperate keys on small keyboards like on most
notebooks. i need to use a
On 11/3/06, Beni Cherniavsky [EMAIL PROTECTED] wrote:
On 30/10/06, Philip Ganchev [EMAIL PROTECTED] wrote:
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
On Fri, Nov 03, 2006 at 04:58:27PM +0200, Axel Liljencrantz wrote:
I guess this is a classic case of something that sounds cool, and
sounds like it may have pitfalls, but you don't really know how well
it works until you try it out in practice.
i like the sound of it, and i'd love to test a
On 11/3/06, Beni Cherniavsky [EMAIL PROTECTED] wrote:
[...]
I see a simple solution: when the cursor was in the first line and you
press Up, you should land you at the *first* line of the previous
command, not the last. Similarly, Down should land you in the last
line of the next command.
On Tue, Oct 31, 2006 at 01:18:57AM +0100, Axel Liljencrantz wrote:
As Philip said, this is not how fish should be behaving. If there are
no matches, pressing up or down should give you the original search
string. If not, that is a bug.
if i edit a previously run command somewhere in the
On Mon, Oct 30, 2006 at 04:52:56PM -0500, Philip Ganchev wrote:
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
On 10/31/06, Martin Bähr [EMAIL PROTECTED] wrote:
On Tue, Oct 31, 2006 at 06:04:32PM +0100, Axel Liljencrantz wrote:
Press the escape key to abort the search.
that will return me to the search string, but it won't give me back what
it threw away,
That is a misfeature. It should be fixed.
On 10/31/06, Martin Bähr [EMAIL PROTECTED] wrote:
On Mon, Oct 30, 2006 at 04:52:56PM -0500, Philip Ganchev wrote:
[...]
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
On Tue, Oct 31, 2006 at 06:04:32PM +0100, Axel Liljencrantz wrote:
Press the escape key to abort the search.
that will return me to the search string, but it won't give me back what
it threw away, and it doesn't exit search mode. the whole string is
still pink.
greetings, martin.
--
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
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
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
12 matches
Mail list logo
