(old)Puppy Linux Discussion Forum

Look at what I found:

TechPosters: Technical Posters and Cheats for IT Guys

Flash :
thanks for the link.....some good info on that site.

OK aragon, it does work. What I copied must have had the keycodes wrong or something.

This doesn't work though:
set completion-ignore-case on

Flash wrote:Look at what I found:

TechPosters: Technical Posters and Cheats for IT Guys

It appears this link is bad - The One Page Linux Manual.pdf (94,28 KB)

aragon wrote: but i will do 2 things:
1. try to optimize (maybe landscape would help)
2. post the base wp-file as flash suggested

I converted the pdf to a 2 page document for OO .... it's so much easier to read now.

Thom

I converted the pdf to a 2 page document for OO .... it's so much easier to read now.

well done, thom. i've not forgotten that, but had some crashes in abiword trying to convert the word-document.

aragon

I really hate to nitpick as I know how much work is involved in producing and proof-reading technical documentation.

However, wildcards added to "dangerous" commands isn't the best idea!

Could you perhaps write "Note 1" in tiny letters or something?

I have printed this off and will be laminating it this evening.

Thanks.

A doubling is definitely in order; the world awaits the 2 paged version. Plus, that way we can sandwich the two pages back to back and laminate to make a nice 2 page computer-side Pupster reference.

tlchost wrote:

ICPUG wrote:That's a nice idea Aragon. I suspect it will expand to 2 sides before long!

It is a super idea....and if it were two-sided, the font size might be increased to allow folks with senior eye sight to enjoy it.

Thom

I just had an idea on the subject:

If I convert it to bare bones HTML and you open it with your browser, the default font size will control the size of the text and the browser will reformat it to make it fit. Paragraphs will word wrap etc. You can then print it with the font size that works best for you.

I'll come back sometime next week and see if anyone thinks I should bother.

i've uploaded a basic-formatted html-version to the first post. if it does work as you've planned? test it!

aragon

aragon wrote:i've uploaded a basic-formatted html-version to the first post. if it does work as you've planned? test it!

Using Opera it's 2 pages with a spill-over onto a third page.

Thom

@Flash, JamesC, tlchost

I tried that info link, but no go.
It seems that they have moved to:

http://techposters.net/

Lots of useful info there...

HTH,

Phil

aragon wrote:i've uploaded a basic-formatted html-version to the first post. if it does work as you've planned? test it!

aragon

The HTML version seems to do it right. It is nice and compact and the web browsers I checked it on liked it just fine. Changing the font size up and down scaled everything as it should.

I tried several browsers that are known to comply with the standards and they all did the same basic stuff.

There are, however, have a few errors.

Right near line 10 and near 401 there should be a <P> and </P> you have text outside of a paragraph.

The "bgcolor" thing is going away. Styles will be the standard soon. For now, I wouldn't bother with that though.

sunburnt wrote:The up arrow key goes back through the commands in rxvt or Xterm.
There`s no way to jump to a command that I know of...

The old Unix command was "!" followed by a letter or 2 of the command you wanted to recall.

So you've entered a bunch of commands, and want to recall a command:

#!ru

goes back in your history and finds:

#runthisverylongcommandsoIdon'thavetorecallthedamnthing

And the command:

#history

will show you a list of your command history

This can then recall a command by (say #285 was "#runthisverylongcommandsoIdon'thavetorecallthedamnthing")

#!285

Which will recall the command (#285):

#runthisverylongcommandsoIdon'thavetorecallthedamnthing

Most people set up an alias file, and alias "h" to history. Keep in mind that these numbers will roll off (change)...

I don't recall what the recall history length is (it might be the last 1000 commands), but the file where the history is stored is in /root/.history

One could also "#grep -i damnthing .history" to display the command above, that is stored inside the .history file.

Thank you Aragon, very helpful

.

Hi all
Thanks very much for the commands, A very useful tool (has helped me loads)
Cheers
Stripe

Tubeguy made a nice online-version: http://tubeguy.org/PLRC-0.01b.html

aragon

aragon wrote:

disciple wrote: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.

This is a fantastic idea, aragon. I just wanted to add my thanks.