Can anyone explain searching through the command history with Ctrl-R? I tried in in cygwin rxvt last night, and it seems you type in the first part of a command, press Ctrl-R, and then press space to search backwards through the history... but now that I try it in Puppy it only seems to find the most recent command, and won't search any further back...

am using it the other way round, first Ctrl+R then type part of the command. the limitation with the most recent command is here also.

aragon

I later found out:
- press Ctrl-R with an empty command line
- type part of the command
- press Ctrl-R again to go to the previous match.
This is very useful; I use it constantly._________________DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!

This is great! I'm trying to learn to use the command line more, but so many of the things I find online or in books work in other distros, but not Puppy. If I see "Bad command or file name" one more time, I'll go postal, LOL!

Thank you for this--the HTML version is especially helpful, as it's the easiest to read, IMHO at least.

Can anyone explain searching through the command history with Ctrl-R? I tried in in cygwin rxvt last night, and it seems you type in the first part of a command, press Ctrl-R, and then press space to search backwards through the history... but now that I try it in Puppy it only seems to find the most recent command, and won't search any further back...

am using it the other way round, first Ctrl+R then type part of the command. the limitation with the most recent command is here also.

aragon

I later found out:
- press Ctrl-R with an empty command line
- type part of the command
- press Ctrl-R again to go to the previous match.
This is very useful; I use it constantly.

This is great! I'm trying to learn to use the command line more, but so many of the things I find online or in books work in other distros, but not Puppy. If I see "Bad command or file name" one more time, I'll go postal, LOL!

Thank you for this--the HTML version is especially helpful, as it's the easiest to read, IMHO at least.

Posted: Mon 30 Jan 2012, 08:39 Post_subject:
find multiple copies of a program in different pathsSub_title: e.g. /usr/bin and /usr/local/bin

Tip:
`which` only tells you about the copy of a program that will actually run if you call it by name (without the full path).
If you need to check whether you have multiple copies of a program in different paths (e.g. /usr/bin and /usr/local/bin), run this

I have this file in my user book. very useful to remember syntax.
awful syntax. and furthermore english awful computing syntax !
Last user manual done was for puppy 4.3.1, wasn't it ? Things have changed a lot. Or better news things have appeared.
Could even somebody translate in Puppy user's manuals from other distros, with correct syntax, obviously ? Great Job !