Re: .gz ??? what, how?
>>John Foster wrote: >On Tue, 1 Jul 1997, Peter S Galbraith wrote: > >> > > This is not readable by an editor. Is there something special about th >e >> > > .gz?? >> > ><> >> (Funny how an non-Debian specific question still generates so many >> responses on this list!) > >Not really. What we have here is a real problem for the newbies. > >To access the documentation you really need to be able to access >the documentation. Then you can determine what is (and isn't) a Debian >specific issue. Having a system which can hold the newbies' hand till >they can walk for themselves has probably never been a design goal for >Debian, but I think that the user base is growing at such a rate that >it could be time... > >Perhaps there should be a quick intro to gzip, zless and zcat in the >opening scripts (just after the first dselect run?). Even better, a quick intro to mc (and make mc a standard admin package.) Dimitri -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
Joost Kooij wrote: > > On Tue, 1 Jul 1997, David Miles wrote: > > > I need to read information in manual.txt > > > > when I went to the /usr/doc/lilo subdirectory, the closest filename that > > resembled this was Manual.txt.gz > > > > This is not readable by an editor. Is there something special about the > > .gz?? > > It is GZipped. you can unzip it with `gunzip', or use `zmore' instead of > `more', or `zless' instead of `less'. Ofcourse, these are all pagers. But > I bet there's some emacs mode to read and write gzipped files. > > `man gzip' is your friend. > > Cheers, > > Joost > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . Trouble? > e-mail to [EMAIL PROTECTED] . Yes, if you put (auto-compression-mode) in your .emacs file, then emacs will automatically unzip/uncompress your file into a buffer. The buffer will be compressed if you keep the .gz/.Z extension when you write it out again. However, if you drop the .gz/.Z extension on writting out, then it will not be compressed. H.C. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
> > To access the documentation you really need to be able to access > > the documentation. Then you can determine what is (and isn't) a Debian > > specific issue. Having a system which can hold the newbies' hand till > > they can walk for themselves has probably never been a design goal for > > Debian, but I think that the user base is growing at such a rate that > > it could be time... > ^ Should ... actually if you want to attract msdog ppl, a "must"! > > > > Perhaps there should be a quick intro to gzip, zless and zcat in the > > opening scripts (just after the first dselect run?). > > Perhaps just a /usr/doc/intro/* section that may actually contain > this and other useful newbie tips > This is a great idea. An index of the documentation is so necessary. I suggest putting this index and some very basic help topics in /etc/skel and propogate them to all users. The file doesn't have to be huge, it should just tell the newbie where to go for more help and how to read it. I spent days looking through my system finding little tidbits here and there. This is one place X really shines, fire up TkDesk and you can see a list of files, double click and pop up what you want in the same window or not. Maybe MC could be adapted to help also (I know this has been discussed before). Also, I would suggest making this file plain txt, so the user could have easier access. Thanks "Change is inevitable, except from a vending machine." Rob MacWilliams [EMAIL PROTECTED] N9NPU -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
> > On Tue, 1 Jul 1997, Peter S Galbraith wrote: > > > > > This is not readable by an editor. Is there something special about the > > > > .gz?? > > > > <> > > (Funny how an non-Debian specific question still generates so many > > responses on this list!) > > Not really. What we have here is a real problem for the newbies. Sure > > To access the documentation you really need to be able to access > the documentation. Then you can determine what is (and isn't) a Debian > specific issue. Having a system which can hold the newbies' hand till > they can walk for themselves has probably never been a design goal for > Debian, but I think that the user base is growing at such a rate that > it could be time... ^ Should ... actually if you want to attract msdog ppl, a "must"! > > Perhaps there should be a quick intro to gzip, zless and zcat in the > opening scripts (just after the first dselect run?). Perhaps just a /usr/doc/intro/* section that may actually contain this and other useful newbie tips Ok, so let's take a previous response: use 'most' ... $ most some_text_file.gz ... fine $ most some_archive.tar.gz ... _not_ yet configured to display the 'listing' ... instead it gives the 'contents' ... not very useful Ok ... having used slip_slop_slackware I can't help comparing the way 'less' is configured there ... not having even known of 'most' and noticing how on the deb-1.2 system I manage that 'less' does not have the same configured functionality as the 'less' on slackware, I simply copied the configs over ... in /etc/profile 3 things: (1) LESS="-M -I" ... and the switches mean -i Causes searches to ignore case; that is, uppercase and lowercase are considered identical. This option is ignored if any uppercase letters appear in the search pattern; in other words, if a pattern contains upper- case letters, then that search does not ignore case. -I Like -i, but searches ignore case even if the pattern contains uppercase letters. -M Causes less to prompt even more verbosely than more. (2) as well as the environment variable for the script that 'less' uses to "pipe" : export LESSOPEN="|lesspipe.sh %s" (3) export PAGER=less Now, that script 'lesspipe.sh' I could not find on the debian system at work, so I ripped it from the slackware one at home, which lives in /usr/bin/lesspipe.sh . And the script is : - cut here --- #!/bin/sh # This is a preprocessor for 'less'. It is used when this environment # variable is set: LESSOPEN="|lesspipe.sh %s" lesspipe() { case "$1" in *.tar) tar tvvf $1 2>/dev/null ;; # View contents of .tar and .tgz files *.tgz) tar tzvvf $1 2>/dev/null ;; *.tar.gz) tar tzvvf $1 2>/dev/null ;; *.tar.Z) tar tzvvf $1 2>/dev/null ;; *.tar.z) tar tzvvf $1 2>/dev/null ;; *.Z) gzip -dc $1 2>/dev/null ;; # View compressed files correctly *.z) gzip -dc $1 2>/dev/null ;; *.gz) gzip -dc $1 2>/dev/null ;; *.zip) unzip -l $1 2>/dev/null ;; *.1|*.2|*.3|*.4|*.5|*.6|*.7|*.8|*.9|*.n|*.man) FILE=`file -L $1` ; # groff src FILE=`echo $FILE | cut -d ' ' -f 2` if [ "$FILE" = "troff" ]; then groff -s -p -t -e -Tascii -mandoc $1 fi ;; # *) FILE=`file -L $1` ; # Check to see if binary, if so -- view with 'strings' #FILE1=`echo $FILE | cut -d ' ' -f 2` #FILE2=`echo $FILE | cut -d ' ' -f 3` #if [ "$FILE1" = "Linux/i386" -o "$FILE2" = "Linux/i386" \ # -o "$FILE1" = "ELF" -o "$FILE2" = "ELF" ]; then # strings $1 #fi ;; esac } lesspipe $1 # eof - cut here --- 'less', for me, still does 'more' than 'most' ;) > > John Foster > Rob - ps: 1st posting here ... I must say documentation, packaging and administration in debian appear to be more 'complete' than in slackware ... unfortunately at this stage I have come over to work with a rather misconfigured debian system ... hoping to get good support here ... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
On Tue, 1 Jul 1997, Peter S Galbraith wrote: > > > This is not readable by an editor. Is there something special about the > > > .gz?? > > <> > (Funny how an non-Debian specific question still generates so many > responses on this list!) Not really. What we have here is a real problem for the newbies. To access the documentation you really need to be able to access the documentation. Then you can determine what is (and isn't) a Debian specific issue. Having a system which can hold the newbies' hand till they can walk for themselves has probably never been a design goal for Debian, but I think that the user base is growing at such a rate that it could be time... Perhaps there should be a quick intro to gzip, zless and zcat in the opening scripts (just after the first dselect run?). John Foster -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
> > This is not readable by an editor. Is there something special about the > > .gz?? > > It is GZipped. you can unzip it with `gunzip', or use `zmore' instead of > `more', or `zless' instead of `less'. Ofcourse, these are all pagers. But > I bet there's some emacs mode to read and write gzipped files. jka-compr Putting the following line in ~/.emacs: (require 'jka-compr) you can then simply edit a gzipped file and Emacs will uncompress it automatically. (Funny how an non-Debian specific question still generates so many responses on this list!) -- Peter Galbraith, research scientist <[EMAIL PROTECTED]> Maurice-Lamontagne Institute, Department of Fisheries and Oceans Canada P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada 418-775-0852 - FAX 418-775-0546 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
David Miles wrote: > > I need to read information in manual.txt > > when I went to the /usr/doc/lilo subdirectory, the closest filename that > resembled this was Manual.txt.gz > > This is not readable by an editor. Is there something special about the > .gz?? > command 'most' will do it. Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
Try: zless file.name.gz (may not need the .gz) or lynx file.name.gz (not sure here either) On Tue, 1 Jul 1997, David Miles wrote: > > I need to read information in manual.txt > > when I went to the /usr/doc/lilo subdirectory, the closest filename that > resembled this was Manual.txt.gz > > This is not readable by an editor. Is there something special about the > .gz?? > > > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . Trouble? > e-mail to [EMAIL PROTECTED] . > > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
.gz -- gzip extension. gzip is a program used to compress files, comparable to .zip files in dos/windows. To un-gzip a file the command is gzip -d filename.gz or gunzip filename.gz, same thing. Then you can read it as a regular text file. I prefer using: zcat filename.gz |less. zcat uncompress the file to standard output for reading and piped through less to control the scroll. This way you can keep your documents compress for storage, without the hastle of uncompressing them all the time. For more info look up manpages on gzip, gunzip, tar, zcat, zgrep... Dennis On Tue, 1 Jul 1997, David Miles wrote: > Date: Tue, 1 Jul 1997 03:57:44 -0600 (MDT) > From: David Miles <[EMAIL PROTECTED]> > To: debian-user@lists.debian.org > Subject: .gz ??? what, how? > Resent-Date: Tue, 1 Jul 1997 13:51:05 -0400 > Resent-From: debian-user@lists.debian.org > > > I need to read information in manual.txt > > when I went to the /usr/doc/lilo subdirectory, the closest filename that > resembled this was Manual.txt.gz > > This is not readable by an editor. Is there something special about the > .gz?? > > > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . Trouble? > e-mail to [EMAIL PROTECTED] . > > + dpk <[EMAIL PROTECTED]> + work : 517.353.8892 + + Systems Undergrad + pager: 517.222.5875 + + Division of Engineering Computing Services + + -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: .gz ??? what, how?
On Tue, 1 Jul 1997, David Miles wrote: > I need to read information in manual.txt > > when I went to the /usr/doc/lilo subdirectory, the closest filename that > resembled this was Manual.txt.gz > > This is not readable by an editor. Is there something special about the > .gz?? It is GZipped. you can unzip it with `gunzip', or use `zmore' instead of `more', or `zless' instead of `less'. Ofcourse, these are all pagers. But I bet there's some emacs mode to read and write gzipped files. `man gzip' is your friend. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
.gz ??? what, how?
I need to read information in manual.txt when I went to the /usr/doc/lilo subdirectory, the closest filename that resembled this was Manual.txt.gz This is not readable by an editor. Is there something special about the .gz?? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .