Re: help, man, etc. (was: Re: Using terminal commands - corner cases)
On 27/11/2024 23:59, to...@tuxteam.de wrote:
OTOH, the venerable groff has gained a hyperlink markup
recently [1] ("recently" in its time scale), thus bridging yet another
gap separating man and info.
Does it affect "man" when called in a terminal application (so usually
"less" is used as a pager)? At least Emacs and Vim use heuristics with
plenty of shortcomings to recognize cross-references to other man pages
(https://manpages.debian.org - debiman works better because it has index
of man pages from all packages). It is even worse with links to other
sections and to notes in the same document.
doc-base maintains some document index for yelp/khelpcenter/dhelp/dochelp.
Re: Adding a new boot disk while keeping old disk
On 11/26/24 01:03, Charlie Gibbs wrote: > But there are no icons left on the desktop - no more Portal, and none of > the utilities I downloaded were on my $PATH. > > How do the rest of you deal with all the user-added stuff that vanishes > when you do a fresh install? Are there some tricks I can use, rather > than painstakingly re-installing all my utilities one by one? If they were installed through a package manager, you probably shouldn't do that. > I assume you can just copy the old /home over to the new drive Mind the dotfiles. Apps might behave strangely when you run them with an old config file. > But that does nothing about all the nifty utilities that > were in (e.g.) /usr/bin (even though the configuration files are probably > in /home). I hate losing stuff and drastic changes like that, so what I've done in the past when I used Ubuntu was: * do a complete backup * clean-install the latest *-LTS version * restore /home, being careful not to overwrite existing dotfiles * restore any other filesystems that aren't part of the base install * modify /etc/profile.d/* to change $PATH as appropriate * keep the installation as long as possible. The last time I went through this I made a list of installed packages (apt list --installed) so I could re-install (some of) them on the new OS. This probably is not the recommended procedure. Since I switched to Debian the issue hasn't come up, so I haven't yet been forced into a decision as to how to deal with it.
Re: Using terminal commands - corner cases
On Wed 27 Nov 2024 at 05:38:30 (-0600), Richard Owlett wrote: > I've used terminal commands for so many decades I don't know where to > look up fine details of a specific commands. > > I just tried to use the cd command with a target directory having > spaces in it's name. Of course the system responded > > bash: cd: too many arguments > > DuckDuckGo led to [ > https://bash.cyberciti.biz/guide/Cd_command#Dealing_with_directories_with_white_space_in_their_names > ]. > > Problem solved. But is there somewhere to go directly without a web search? Well, it strikes me that, with the exception of Greg's, all these posts are about man, info, help, etc., which you probably know about already, whereas what your error above shows is that you need some passing knowledge of the contents of man bash. If you find that rather dry and indigestible, you might try running: $ wget http://folk.ntnu.no/geirha/bashguide.pdf which gives you a guide that's designed more for reading than as a reference document. BTW I find large man pages a little more navigable by running, eg: $ man -t bash | ps2pdf - /tmp/bash.pdf though that might not be suitable for the OP. Cheers, David.
Re: WHOIS rejection from strange IP address
On Wed, Nov 27, 2024 at 4:27 AM George at Clug wrote: > > Curiosity got the better of me, so I installed "whois" and gave it a try. > > Below are the responses I get, for "$whois 191.96.36.56" and I tried a whois > on the ip in "%ERROR:201: access denied for 190.112.52.14" > > I wonder what this information might mean to anyone? How would this > information be useful? You get their tech contact, so you can ask about problems accessing something in their network or let them know about their open ntp server that can be used for DOS attacks or .. whatever. You also get their abuse contact info so you know where to direct emails about abusive behavior from that ip address range. If whois will look up handles you can lookup the abuse handle. I can't figure out how to do that so https://search.arin.net/rdap/?query=162.142.125.0 which gives me their abuse info https://about.censys.io/ which leads to https://support.censys.io/hc/en-us/articles/360043177092-Opt-Out-of-Data-Collection which allows me to "opt-out" of their abusive scanning by putting their list of subnets into my firewall block list. Regards, Lee
Re: help, man, etc. (was Re: Using terminal commands - corner cases)
On Wed, Nov 27, 2024 at 11:03:48AM -0500, Greg Wooledge wrote: > On Wed, Nov 27, 2024 at 10:40:44 -0500, The Wanderer wrote: > > One of the items on the list, under the characteristics of a > > "knowledgeable user", is the entry: > > > > * has learned that learn doesn't help > > > > I have never managed to find out what 'learn' is supposed to have been. > > No Linux or other *nix-derived system I've ever used has had a command > > by that name. > > https://www.unix.com/man-page/bsd/1/LEARN/ Wow :-) Cheers -- t signature.asc Description: PGP signature
Re: The "uniqueness" of UUIDs
On Tue, Nov 26, 2024 at 04:35:13PM +0100, Roger Price wrote: My understanding is that a Linux file system is a hierachical structure starting with the root directory (/) which organises the directories and files. The files are stored on various devices which have identities such as /dev/sdxn, UUID or LABEL. These identities are for the devices, not parts of the file system. Your understanding is wrong: the UUIDs you are talking about are a feature of the filesystem--that's why they appear in lsblk -f (filesystem) output. You can find the same UUID in filesystem-specific tools such as dumpe2fs; lsblk has logic to extract a UUID from each filesystem that it knows how to parse and which contains a UUID. There are other UUIDs associated with some storage devices, partitions, and all sorts of other things on a modern system, but they are not the filesystem UUID and are not what is displayed in lsblk -f. (lsblk -f does include some UUIDs which aren't in filesystems, but which are in some other on-disk structure logically similar to a filesystem; an example is LVM physical volumes [also visible via pvs -v].)
Re: help, man, etc. (was Re: Using terminal commands - corner cases)
On Wed, Nov 27, 2024 at 10:40:44AM -0500, The Wanderer wrote:
> On 2024-11-27 at 09:28, to...@tuxteam.de wrote:
[...]
> > And yes, it's a pity there is no common frontend for both.
[help and man]
>
> There's also 'info foo', which for some values of foo will be more
> helpful than either of the above, for others will provide exactly the
> same information through a different interface, and for others will
> provide no information at all.
The nice thing about info is that it /actually/ falls back to the man
page when no info page is available. So it is a common front-end of
sorts for both. OTOH, the venerable groff has gained a hyperlink markup
recently [1] ("recently" in its time scale), thus bridging yet another
gap separating man and info.
[...]
> * has learned that learn doesn't help
[...]
> Does anyone have an idea what this old reference may be talking about?
Although I did some first Unix steps on a "real" AT&T (a port for M68K),
with ksh (and a vi which dumped core on lines >1K!), I have no clue,
sorry.
Cheers
--
t
signature.asc
Description: PGP signature
Re: help, man, etc. (was Re: Using terminal commands - corner cases)
On Wed, Nov 27, 2024 at 12:24:25PM -0500, The Wanderer wrote: > On 2024-11-27 at 11:59, to...@tuxteam.de wrote: > > > On Wed, Nov 27, 2024 at 10:40:44AM -0500, The Wanderer wrote: > > > >> On 2024-11-27 at 09:28, to...@tuxteam.de wrote: > > >>> And yes, it's a pity there is no common frontend for both. > > > [help and man] > > >> There's also 'info foo', which for some values of foo will be more > >> helpful than either of the above, for others will provide exactly > >> the same information through a different interface, and for others > >> will provide no information at all. > > > > The nice thing about info is that it /actually/ falls back to the > > man page when no info page is available. So it is a common front-end > > of sorts for both. > > ...huh. So it does, apparently. > > Even at this point I still live and learn. I always thought it was just > that a few particular packages had had their man pages blindly converted > to info format so the packager could ship documentation in both formats. > > To be honest, I think I'd kind of rather that it didn't do that... but > it's not like it's hard to recognize the converted-from-man-page > presentation and quit the viewer, when it does happen. It tells you, though. For example, if I do "info ldd", apart from the giveaway in the heading, as you observe, the footer page says: -Info: (*manpages*)ldd, 65 lines --Top--- So it ain't cheating, honest ;-) Cheers -- t signature.asc Description: PGP signature
Re: Using terminal commands - corner cases
And, just for the record, should you want to find out more about commands on Linux without leaving your system (i.e. without any interaction with the Internet at all), the man command is available to present the manual pages (dates back to when there was an actual manual in early unix days) for individual commands, e.g. man bash which will describe in quite some detail how to use the shell and man -k somekeyword will allow to search man pages. bash itself also has a help system: type "help" :-) -- Eric S Fraga via gnus (Emacs 31.0.50 2024-08-16) on Debian 12.6
Re: Using terminal commands - corner cases
On Wed, Nov 27, 2024 at 12:55:10 +0100, to...@tuxteam.de wrote: > First: cd is not a command, it is a shell builtin > (this is subtle, but important). It's both. You can even call it a "builtin command". > Second: even if cd were a "command", the splitting > of args at whitespace (among *a lot* of other things) > is done by the shell before the command has even a > chance at it. Yes. The shell *parses* each command you type, and among the steps taken by the parser, one of the most basic is tokenizing the input into words. Given a command like this: cd /mnt/c/Program Files the tokenizer breaks it into words: [cd] [/mnt/c/Program] [Files] The first word will be the name of the command to run, and all the words after that will be arguments passed to the command. If you want "Program Files" to be treated as a single word, then you must use quoting. There are several forms, and they're all acceptable: cd "/mnt/c/Program Files" cd '/mnt/c/Program Files' cd /mnt/c/Program\ Files cd /mnt/c/"Program Files" In all four cases, the tokenizer only sees two words: [cd] [/mnt/c/Program Files] (A second parsing step is quote removal, which discards the quoting characters that were used to aid the tokenization.) Also just for the record, bash's tab completion feature is extremely helpful. If you type just "cd /mnt/c/Pro" and then press the Tab key, it will look at the actual file system and find files or directories that match the current partial word. If there's only one match, then it'll type out the rest of the filename for you. If there are multiple matches, the behavior depends on your settings. You may need to press Tab a second time to get a list of the matches, so that you can type more characters to make your partial word have only a single match. When tab completion auto-types a filename with whitespace in it, it'll use the backslash quoting form to mark the spaces as literal characters rather than word separators.
Re: help, man, etc. (was Re: Using terminal commands - corner cases)
On 2024-11-27 at 11:59, to...@tuxteam.de wrote: > On Wed, Nov 27, 2024 at 10:40:44AM -0500, The Wanderer wrote: > >> On 2024-11-27 at 09:28, to...@tuxteam.de wrote: >>> And yes, it's a pity there is no common frontend for both. > [help and man] >> There's also 'info foo', which for some values of foo will be more >> helpful than either of the above, for others will provide exactly >> the same information through a different interface, and for others >> will provide no information at all. > > The nice thing about info is that it /actually/ falls back to the > man page when no info page is available. So it is a common front-end > of sorts for both. ...huh. So it does, apparently. Even at this point I still live and learn. I always thought it was just that a few particular packages had had their man pages blindly converted to info format so the packager could ship documentation in both formats. To be honest, I think I'd kind of rather that it didn't do that... but it's not like it's hard to recognize the converted-from-man-page presentation and quit the viewer, when it does happen. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Using terminal commands - corner cases
On Wed, Nov 27, 2024 at 02:18:02PM +, Eric S Fraga wrote: > And, just for the record, should you want to find out more about > commands on Linux without leaving your system (i.e. without any > interaction with the Internet at all), the man command is available to > present the manual pages (dates back to when there was an actual manual > in early unix days) for individual commands, e.g. > > man bash > > which will describe in quite some detail how to use the shell and > > man -k somekeyword > > will allow to search man pages. > > bash itself also has a help system: type "help" :-) Good points -- as a tip, turn things around: first try "help foo", then "man foo" whenever you don't know whether what you have is a builtin or a command. And yes, it's a pity there is no common frontend for both. Cheers -- t signature.asc Description: PGP signature
Re: Using terminal commands - corner cases
On Wed, 27 Nov 2024 14:36:44 +0100 wrote: > On Wed, Nov 27, 2024 at 07:30:17AM -0600, Richard Owlett wrote: > > [...] > > > Thank you. I've seen his site before. I just created a bookmark > > folder for "Debian Wikis". The first occupant > > is https://mywiki.wooledge.org . > > Greg's wiki is a jewel. I thank *him* for it. > > > I've been a computer *user* for six of my eight decades. > > My only formal background was a one semester intro to programming > > course as a freshman E.E. student. > > [...] > > Now what programming language was this? > I would guess most of us in engineering started with some variant of Fortran. Mine was on an ICL1907 mainframe, which I never saw. IBM 80 column card punches... -- Joe
Re: Using terminal commands - corner cases
On 11/27/24 7:36 AM, to...@tuxteam.de wrote: On Wed, Nov 27, 2024 at 07:30:17AM -0600, Richard Owlett wrote: [...] Thank you. I've seen his site before. I just created a bookmark folder for "Debian Wikis". The first occupant is https://mywiki.wooledge.org . Greg's wiki is a jewel. I thank *him* for it. I've been a computer *user* for six of my eight decades. My only formal background was a one semester intro to programming course as a freshman E.E. student. [...] Now what programming language was this? CORC/CUPL https://en.wikipedia.org/wiki/Cornell_University_Programming_Language Dartmouth's BASIC was more popular. But we had better football ;/ Cheers
Re: Using terminal commands - corner cases
Le 11/27/24 à 15:18, Eric S Fraga a écrit : [...] the man command is available to present the manual pages There are also the fine info pages for most gnu software, notably the coreutils, and the /usr/share/doc directory for most other software. Best, -- yassine -- sysadm +213-779 06 06 23 http://about.me/ychaouche
help, man, etc. (was Re: Using terminal commands - corner cases)
On 2024-11-27 at 09:28, to...@tuxteam.de wrote: > On Wed, Nov 27, 2024 at 02:18:02PM +, Eric S Fraga wrote: > >> And, just for the record, should you want to find out more about >> commands on Linux without leaving your system (i.e. without any >> interaction with the Internet at all), the man command is available >> to present the manual pages (dates back to when there was an actual >> manual in early unix days) for individual commands, e.g. >> >> man bash >> >> which will describe in quite some detail how to use the shell and >> >> man -k somekeyword >> >> will allow to search man pages. >> >> bash itself also has a help system: type "help" :-) > > Good points -- as a tip, turn things around: first try "help foo", > then "man foo" whenever you don't know whether what you have is a > builtin or a command. > > And yes, it's a pity there is no common frontend for both. There's also 'info foo', which for some values of foo will be more helpful than either of the above, for others will provide exactly the same information through a different interface, and for others will provide no information at all. This (multiple commands to find the documentation for a command, with no unified way to look in all the places at once) reminds me of something that's been in the back of my mind for a long time, and which I've occasionally gone looking about, but never managed to find an answer on/for. There is a document which I apparently don't have locally, and don't remember where I first found, but which is still hosted (in various formats, none of which are quite what I remember having seen, though the contents match) in various locations on the current Web. I remember its having been called "Draft of the UNIX Hierarchy". One location for it which I find in searching today is: https://www.cs.earlham.edu/~skylar/humor/Unix/unix.hierarchy.html Many of the items it lists are obsolete regarding modern usage of, knowledge of, and familiarity with Linux, and in terms of the developments in the culture of the use of UNIX and its derivatives over the time since the document was written, but many of them are still sufficiently on point to be understandable as reference points. (As a side note, I would be interested in seeing - and might be interested in helping to write - an updated version of such a list.) When I first read this document, there were many references on it which I did not understand. (One prominent example: I did not know who Dennis, Bill, and Ken were.) Since then, I have managed to educate myself sufficiently to be able to understand nearly all of them - with one prominent exception. One of the items on the list, under the characteristics of a "knowledgeable user", is the entry: * has learned that learn doesn't help I have never managed to find out what 'learn' is supposed to have been. No Linux or other *nix-derived system I've ever used has had a command by that name. I've never managed to find a document which mentions it in a way that would give a hint as to in what context the term would have existed, or what it would have been *supposed to* do (whether or not it actually did it). Does anyone have an idea what this old reference may be talking about? -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Email Problem
I think I might have contracted a virus, but I'm not sure. I am running Bookworm and have been using the Epyrus email client for some time now without any problems. Suddenly I am getting a popup that is quite insistent. I have run ClamTk on /home/comp and /opt/epyrus, both are clean. The source of the email is my web Page, which I have temporarily removed from my Hosting Service, but the popup continues to appear. Where else might the errant string of DNA or RNA be hiding on my computer? Guidance would be much appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. https://insilicochemistry.net (614)312-7528 (c) Skype: smolnar1
Re: Using terminal commands - corner cases
Eric S Fraga wrote: > And, just for the record, should you want to find out more about > commands on Linux without leaving your system (i.e. without any > interaction with the Internet at all), the man command is available to > present the manual pages (dates back to when there was an actual manual > in early unix days) for individual commands, e.g. > > man bash > > which will describe in quite some detail how to use the shell and > The bash man page is often rather too lengthy to find what one wants easily. For bash built-in commands it's often more useful to try 'help ' as you don't then have to wade through the *huge* bash man page to find what you want. For example 'help cd' gives a nice man page like summary of how to use cd. -- Chris Green ·
Re: help, man, etc. (was Re: Using terminal commands - corner cases)
On Wed, Nov 27, 2024 at 10:40:44 -0500, The Wanderer wrote: > One of the items on the list, under the characteristics of a > "knowledgeable user", is the entry: > > * has learned that learn doesn't help > > I have never managed to find out what 'learn' is supposed to have been. > No Linux or other *nix-derived system I've ever used has had a command > by that name. https://www.unix.com/man-page/bsd/1/LEARN/
Re: Email Problem
On Wed, 27 Nov 2024 10:50:33 -0500
"Stephen P. Molnar" wrote:
Hello Stephen,
>Where else might the errant string of DNA or RNA be hiding on my
>computer?
https://forum.palemoon.org/viewtopic.php?f=73&t=31786
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Black man got a lot of problems, but he don't mind throwing a brick
White Riot - The Clash
pgpX2R8eqa1zc.pgp
Description: OpenPGP digital signature
Re: Email Problem
Stephen, Can you please provide a bit more detail and your setup. To me the issue maybe DNS record related, but I am not sure. I am guessing mail.stackmail.com certificate has expired or is self-signed? But I am not sure how to check this. Do you use any DNS caching on your computer? Can you try a different computer? Is insilicochemistry.net your web site, and do you also have one or more MX records (insilicochemistry.net, and mail.insilicochemistry.net) in your web site's DNS that point to mail.stackmail.com ? Below is some DNS name checking that I did, the results confuse me. I am guessing that your web site insilicochemistry.net is hosted on scluster24.stablehost.com and your email server is hosted on mail.stackmail.com? If so, what happens if in your Epyrus email client, you use mail.stackmail.com and not mail.insilicochemistry.net ? Epyrus is not packaged with Debian, hence I expect that you downloaded it and installed it? http://www.epyrus.org/ https://mxtoolbox.com/SuperTool.aspx?action=mx%3ainsilicochemistry.net&run=toolpage PrefHostnameIP Address 10 mx.stackmail.com185.151.28.67 $ dig mx mail.insilicochemistry.net +short mail.stackmail.com. gkirkham@debkde05:~$ dig mx insilicochemistry.net +short $ dig -x 213.109.149.117 +short scluster24.stablehost.com. $ nslookup insilicochemistry.net Non-authoritative answer: Name: insilicochemistry.net Address: 213.109.149.117 $ nslookup insilicochemistry.net -type=mx Non-authoritative answer: Name: insilicochemistry.net Address: 213.109.149.117 $ nslookup 213.109.149.117 117.149.109.213.in-addr.arpaname = scluster24.stablehost.com. $ nslookup 213.109.149.117 -type=mx Non-authoritative answer: 117.149.109.213.in-addr.arpaname = scluster24.stablehost.com. $ nslookup mail.insilicochemistry.net Non-authoritative answer: mail.insilicochemistry.net canonical name = mail.stackmail.com. Name: mail.stackmail.com Address: 185.151.28.68 Name: mail.stackmail.com Address: 185.151.28.84 Name: mail.stackmail.com Address: 185.151.28.85 $ nslookup mail.insilicochemistry.net -type=mx Non-authoritative answer: mail.insilicochemistry.net canonical name = mail.stackmail.com. Name: mail.stackmail.com Address: 185.151.28.68 Name: mail.stackmail.com Address: 185.151.28.84 Name: mail.stackmail.com Address: 185.151.28.85 https://www.stablehost.com/about-us.php $ nslookup scluster24.stablehost.com -type=mx Non-authoritative answer: Name: scluster24.stablehost.com Address: 213.109.149.116 $ nslookup 213.109.149.116 116.149.109.213.in-addr.arpaname = scluster24.stablehost.com. $ ping 185.151.28.68 PING 185.151.28.68 (185.151.28.68) 56(84) bytes of data. 64 bytes from 185.151.28.68: icmp_seq=1 ttl=45 time=296 ms 64 bytes from 185.151.28.68: icmp_seq=2 ttl=45 time=296 ms ^C --- 185.151.28.68 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 296.197/296.311/296.425/0.114 ms $ nslookup 185.151.28.68 68.28.151.185.in-addr.arpa name = smtp.stackmail.com. $ nslookup 185.151.28.85 85.28.151.185.in-addr.arpa name = 185-151-28-85.ptr4.stackcp.net. https://mxtoolbox.com/SuperTool.aspx?action=mx%3amail.insilicochemistry.net&run=toolpage TypeDomain Name Canonical Name TTL CNAME mail.insilicochemistry.net mail.stackmail.com 60 min Blacklist Check SMTP Test TestResult Status Problem DMARC Record Published No DMARC Record found Information More Info Status Warning DMARC Policy Not EnabledDMARC Quarantine/Reject policy not enabled Information More Info Status Ok DNS Record PublishedDNS Record found https://mxtoolbox.com/SuperTool.aspx?action=smtp%3amail.insilicochemistry.net&run=toolpage https://mxtoolbox.com/emailhealth/mail.insilicochemistry.net/ 5 Problems CategoryHostResult Status Problem dmarc insilicochemistry.net No DMARC Record found information More Info Status Problem mx insilicochemistry.net No DMARC Record found information More Info Status Warning mx insilicochemistry.net DMARC Quarantine/Reject policy not enabled information More Info Status Warning smtpmx.stackmail.comReverse DNS does not match SMTP Banner information More Info Status Warning dns insilicochemistry.net SOA Serial Number Format is Invalid information More Info On Thursday, 28-11-2024 at 02:50 Stephen P. Molnar wrote: > I think I might have contracted a virus, but I'm not sure. I am running > Bookworm and have been using the Epyrus email client for some time now > without any problems. > > Suddenly I am getting a popup that is quite insistent. > > > > I have run ClamTk on /home/comp and /opt/epyrus, both are clean. The > source of the email is my web Page, which I have temporarily removed > from my Hosting Service, but the popup continues to appear. > > Where else might the e
Re: help, man, etc. (was: Re: Using terminal commands - corner cases)
On Thu, Nov 28, 2024 at 09:34:24AM +0700, Max Nikulin wrote:
> On 27/11/2024 23:59, to...@tuxteam.de wrote:
> > OTOH, the venerable groff has gained a hyperlink markup
> > recently [1] ("recently" in its time scale), thus bridging yet another
> > gap separating man and info.
>
> Does it affect "man" when called in a terminal application (so usually
> "less" is used as a pager)?
Not magically, I guess. I think we'll still need the viewers being able
to "use" the new markup and the footwork of updating the docs.
> At least Emacs and Vim use heuristics with
> plenty of shortcomings to recognize cross-references to other man pages
> (https://manpages.debian.org - debiman works better because it has index of
> man pages from all packages). It is even worse with links to other sections
> and to notes in the same document.
>
> doc-base maintains some document index for yelp/khelpcenter/dhelp/dochelp.
No, I think that new markup is just a way of replacing the heuristic
with knowledge. The knowledge still has to come in :-)
Cheers
--
t
signature.asc
Description: PGP signature
Using terminal commands - corner cases
I've used terminal commands for so many decades I don't know where to look up fine details of a specific commands. I just tried to use the cd command with a target directory having spaces in it's name. Of course the system responded > bash: cd: too many arguments DuckDuckGo led to [ https://bash.cyberciti.biz/guide/Cd_command#Dealing_with_directories_with_white_space_in_their_names ]. Problem solved. But is there somewhere to go directly without a web search? TIA
Re: Using terminal commands - corner cases
On Wed, Nov 27, 2024 at 05:38:30AM -0600, Richard Owlett wrote: > I've used terminal commands for so many decades I don't know where to look > up fine details of a specific commands. > > I just tried to use the cd command with a target directory having spaces in > it's name. Of course the system responded > > bash: cd: too many arguments > > DuckDuckGo led to [ > https://bash.cyberciti.biz/guide/Cd_command#Dealing_with_directories_with_white_space_in_their_names > ]. > > Problem solved. But is there somewhere to go directly without a web search? First: cd is not a command, it is a shell builtin (this is subtle, but important). Second: even if cd were a "command", the splitting of args at whitespace (among *a lot* of other things) is done by the shell before the command has even a chance at it. So for both reasons, it's not "cd" what you are looking at, but your shell. You could do worse than having a look at the Bash Guide, co-maintained by one of our regulars here. For your case, the first chapter [1] seems relevant. Cheers [1] https://mywiki.wooledge.org/BashGuide/CommandsAndArguments -- t signature.asc Description: PGP signature
Re: Using terminal commands - corner cases
On 11/27/24 5:55 AM, to...@tuxteam.de wrote: On Wed, Nov 27, 2024 at 05:38:30AM -0600, Richard Owlett wrote: I've used terminal commands for so many decades I don't know where to look up fine details of a specific commands. I just tried to use the cd command with a target directory having spaces in it's name. Of course the system responded > bash: cd: too many arguments DuckDuckGo led to [ https://bash.cyberciti.biz/guide/Cd_command#Dealing_with_directories_with_white_space_in_their_names ]. Problem solved. But is there somewhere to go directly without a web search? First: cd is not a command, it is a shell builtin (this is subtle, but important). Second: even if cd were a "command", the splitting of args at whitespace (among *a lot* of other things) is done by the shell before the command has even a chance at it. So for both reasons, it's not "cd" what you are looking at, but your shell. You could do worse than having a look at the Bash Guide, co-maintained by one of our regulars here. For your case, the first chapter [1] seems relevant. Cheers [1] https://mywiki.wooledge.org/BashGuide/CommandsAndArguments Thank you. I've seen his site before. I just created a bookmark folder for "Debian Wikis". The first occupant is https://mywiki.wooledge.org . I've been a computer *user* for six of my eight decades. My only formal background was a one semester intro to programming course as a freshman E.E. student. Keep running into things I never knew or had long forgotten ;/ [Only been around Linux since Stretch]
Re: Using terminal commands - corner cases
On Wed, Nov 27, 2024 at 07:30:17AM -0600, Richard Owlett wrote: [...] > Thank you. I've seen his site before. I just created a bookmark folder for > "Debian Wikis". The first occupant is https://mywiki.wooledge.org . Greg's wiki is a jewel. I thank *him* for it. > I've been a computer *user* for six of my eight decades. > My only formal background was a one semester intro to programming course as > a freshman E.E. student. [...] Now what programming language was this? Cheers -- t signature.asc Description: PGP signature
