Copying from the web is faster in most cases: add google_api_key to your google maps templates (they made the key mandatory in 2017) find /home/Albums/NeueBilder/ -name Karte.htt -exec sed -i -e 's/google_api_key\ =\ '\'''\''/google_api_key\ =\ '\''A.The * metacharacter in BRE 1s, ERE 1s and PCRE 1s matches 0 or more occurences of the previously grouped pattern (if a grouped pattern is preceding the * metacharacter), 0 or more occurences of the previous character class (if a character class is preceding the * metacharacter) or 0 or more occurences of the previous character (if neither a grouped pattern nor a character class is preceding the * metacharacter) bash does: When done the command is run: ĭon’t try to figure out yourself. Any shell preprocesses the command line in its own way. And not only was the question about bash instead of rpm, there was also no “weirdness” Using Unix/Linux has a steep learning curve. I can not help it, but those “using the CLI” should know, or at least know where to find, the documentation (man page) of the shell they are using. It matters what you are using as intermediate between you and the kernel. That is why I stressed “bash” a few times instead of only saying “shell”. Unix/Linux will do what you tell it to do, not what you think you tell it to do. ![]() Search for YaST packages (quote the string to prevent the shell from expanding the wildcard).īut most people simply start typing in the shell without thinking about the fact that they are typing in the shell. ![]() If you use blanks around the operator you need to quote the string or escape the blanks according to the rules of the shell you are using. Those who wrote the zypper man page are very nice to their readers by mentioning several times in that page things like That also is able to use * as a wild character in certain cases. We see this often happening the same with the zypper command. Most probably resulting in package names that do not exist. In the case that python* really expands into one or more file names, simply because they are in the working directory, those name(s) wil be fed as argument(s) to the rpm command. It a case of pure luck, but not a case of knowing how the shell works. In most cases there is no file that fits pidgin* and thus the result of the bash expansion is pigin* and that is fed as an argument to the rpm command. ![]() It depends on the result of the “file expansion” done by bash. I tried this on my sandbox PC as well as on my workstation, with the same result.Īnybody can offer an explanation for this mysterious behavior? The expected behavior here is to list all packages whose names begin with the “python” character string. **python**3-urllib3-1.24-lp152.5.3.1.noarchĪnd here comes the weird thing: # rpm -qa python* ![]() Now let’s try the same thing with “python” instead of “pidgin”: # rpm -qa | grep python Here’s a different way to do this: # rpm -qa pidgin* It looks like when I use rpm with the * wildcard, it will work with some packages, but not all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |