Ed Greshko wrote:
On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan
<pocallaghan(a)gmail.com>
wrote:
> On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote:
>> [egreshko@meimei ~]$ rpm -qa pulse*
>> pulseaudio-11.1-18.fc28.1.x86_64
>> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>> pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>> pulseaudio-libs-11.1-18.fc28.1.x86_64
>> pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>> pulseaudio-utils-11.1-18.fc28.1.x86_64
>>
>> [egreshko@meimei ~]$ rpm -qa *pulse*
>> pulseaudio-11.1-18.fc28.1.x86_64
>> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>> alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64
>> pulseaudio-module-x11-11.1-18.fc28.1.x86_64
>> pulseaudio-libs-11.1-18.fc28.1.x86_64
>> kde-settings-pulseaudio-28.0-2.fc28.noarch
>> pulseaudio-libs-glib2-11.1-18.fc28.1.x86_64
>> pulseaudio-utils-11.1-18.fc28.1.x86_64
>>
>> Works fine here. No escaping needed. Not that it matters
>
> The escaping is a precaution. Your example wouldn't work if you had a
> filename starting with 'pulse' in the current directory.
Yeah, but I'm always aware of that possibly. So it's never an issue for me.
I like less typing 😁
It's your choice to use commands which depend on the state
of your current directory, of course. But it's a very bad
habit to teach anyone reading this list who may not yet know
the details of shell glob expansion. There are far better
ways to save two characters in the shell.
When you ask someone to run a command and they don't get the
output you think they should because their current directory
has files matching the unquoted glob, then you haven't saved
them or yourself any typing.
Please, think of the bits! :)
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When we remember we are all mad, the mysteries of life disappear and
life stands explained.
-- Mark Twain