Joe Zeff wrote:
> On 6/4/21 2:05 PM, Samuel Sieb wrote:
>>
>> You removed your text when quoting my email. In the email I replied to,
>> you were quoting the grep line. No mention of rm at all.
>
> We were, and are discussing the way rm acts in a shell script, so I expected
> that rm was the im
On Fri, Jun 04, 2021 at 10:00:17PM +0200, Patrick Dupre wrote:
Patrick Dupre wrote:
> Sorry, I am a bit of list
> This command line works in a shell, but not in a bash
> I may miss some quotes !
> Thanks for your help.
>
> /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
The !(ZMAT*|...) syntax r
On 6/4/21 2:05 PM, Samuel Sieb wrote:
You removed your text when quoting my email. In the email I replied to,
you were quoting the grep line. No mention of rm at all.
We were, and are discussing the way rm acts in a shell script, so I
expected that rm was the implied command.
Samuel Sieb wrote:
> On 2021-06-04 1:00 p.m., Patrick Dupre wrote:
>> How can I leave this mode extglob ?
>
> Do you need to? It will only apply to the rest of the script anyway.
True.
Though depending on the size of the script and what else it
does, there are certainly times when you don't wan
Could you not simply \ escape the ! ?
On Fri, Jun 4, 2021, 3:05 PM Samuel Sieb wrote:
> On 2021-06-04 12:36 p.m., Joe Zeff wrote:
> > On 6/4/21 1:11 PM, Samuel Sieb wrote:
> >>
> >> Which man page? For grep, the "-v" is for inverting the result to
> >> only show non-matching lines.
> >
> > The
On 2021-06-04 1:00 p.m., Patrick Dupre wrote:
How can I leave this mode extglob ?
Do you need to? It will only apply to the rest of the script anyway.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...
On 2021-06-04 12:36 p.m., Joe Zeff wrote:
On 6/4/21 1:11 PM, Samuel Sieb wrote:
Which man page? For grep, the "-v" is for inverting the result to
only show non-matching lines.
The man page for rm, of course. Why would I suggest that you look at
any other command's man page to find out wha
Fantastic,
Thanks.
How can I leave this mode extglob ?
>
> Patrick Dupre wrote:
> > Sorry, I am a bit of list
> > This command line works in a shell, but not in a bash
> > I may miss some quotes !
> > Thanks for your help.
> >
> > /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
>
> The !(ZMAT*|...
Hi,
Patrick Dupre wrote:
> Sorry, I am a bit of list
> This command line works in a shell, but not in a bash
> I may miss some quotes !
> Thanks for your help.
>
> /usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
The !(ZMAT*|...) syntax requires the bash extglob option.
This must be explicitly ena
On 6/4/21 1:17 PM, wwp wrote:
-V, --version
-v, --invert-match
Yes, that's true for grep, but we're discussing rm here.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedorapr
On 6/4/21 1:11 PM, Samuel Sieb wrote:
Which man page? For grep, the "-v" is for inverting the result to only
show non-matching lines.
The man page for rm, of course. Why would I suggest that you look at
any other command's man page to find out what an option for rm means?
It works fine in a command line,
but in a script, I get
#!/bin/bash
/usr/bin/rm -v !(GENBAS|fja.*|run.sh|test.sh|ZMAT*|out*)
./test.sh: line 2: syntax error near unexpected token `('
./test.sh: line 2: `/usr/bin/rm -v !(GENBAS|fja.*|run.sh|test.sh|ZMAT*|out*)'
[jwesterd@jwesterd-f
Hello Joe,
On Fri, 4 Jun 2021 13:04:20 -0600 Joe Zeff wrote:
> On 6/4/21 12:21 PM, Joe Wulf via users wrote:
> > The structure within the paren's looks like what would be used for a >
> > 'grep -Ev' to find everything BUT that mix of patterns.
>
> Checking with the man page, I find that -v
On 2021-06-04 12:04 p.m., Joe Zeff wrote:
On 6/4/21 12:21 PM, Joe Wulf via users wrote:
The structure within the paren's looks like what would be used for a
'grep -Ev' to find everything BUT that mix of patterns.
Checking with the man page, I find that -v stands for verbose, telling
you what'
On 6/4/21 12:21 PM, Joe Wulf via users wrote:
The structure within the paren's looks like what would be used for a
'grep -Ev' to find everything BUT that mix of patterns.
Checking with the man page, I find that -v stands for verbose, telling
you what's happening.
_
[jwesterd@jwesterd-f33 aaa]$ ls -1
a
b
c
d
e
f
[jwesterd@jwesterd-f33 aaa]$ /usr/bin/rm -v !(a*|b*|c*|d*|e*)
removed 'f'
[jwesterd@jwesterd-f33 aaa]$ ls -1
a
b
c
d
e
[jwesterd@jwesterd-f33 aaa]$ echo $0
bash
seems to work?
Are there asterisks or quotes in the files you are affecting?
Cheers
I would have coded it this way:
/usr/bin/rm -v `ls -1|egrep -ve '(^ZMAT|^out|^Out|^GENBAS|^Note)'`
And bash is a shell, but you mean a script. Likely in interactive bash the
* are getting expanded so you might have to use noglob to suppress it or
something similar.
Or you might have to use a sin
Patrick,
The structure within the paren's looks like what would be used for a 'grep -Ev'
to find everything BUT that mix of patterns.
Can you explain what it is you are attempting to do, and provide some context,
please.
Thank you.-Joe
On Friday, June 4, 2021, 2:14:53 PM EDT, Patrick Dupre
Hello,
Sorry, I am a bit of list
This command line works in a shell, but not in a bash
I may miss some quotes !
Thanks for your help.
/usr/bin/rm -v !(ZMAT*|out*|Out*|GENBAS|Note*)
===
Patrick DUPRÉ
On 5/15/19 10:02 AM, francis.montag...@inria.fr wrote:
Me too, and particularly since I discovered the M-/ (or Alt-/,
complete-filename) key to force a simple filename completion when the
full (too fancy) completion with TAB is not what you want.
Thank you very much for this tip! I used this y
On 15/05/2019 06:33, Tom Horsley wrote:
Try removing PackageKit-command-not-found if you don't want that
"feature".
On my list to remove even before I first boot a newly
installed fedora (from a chroot into the fedora partition).
bash-completion and environment-modules are two other
highly irr
Hi
On Wed, 15 May 2019 11:45:51 +0100 Patrick O'Callaghan wrote:
> On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
>> On my list to remove even before I first boot a newly
>> installed fedora (from a chroot into the fedora partition).
>> bash-completion and environment-modules are two other
On Tue, 2019-05-14 at 18:33 -0400, Tom Horsley wrote:
> On Tue, 14 May 2019 18:11:45 -0400
> DJ Delorie wrote:
>
> > Try removing PackageKit-command-not-found if you don't want that
> > "feature".
>
> On my list to remove even before I first boot a newly
> installed fedora (from a chroot into the
On Tue, 14 May 2019, Samuel Sieb wrote:
> On 5/14/19 3:00 PM, Robert P. J. Day wrote:
> >i'm finally annoyed enough about this to just ask ... on a regular
> > basis, i mistype a command and (predictably) get:
> >
> >bash: xxx: command not found...
> >
> > but, quite often, rather than get
On Tue, 14 May 2019 18:11:45 -0400
DJ Delorie wrote:
> Try removing PackageKit-command-not-found if you don't want that
> "feature".
On my list to remove even before I first boot a newly
installed fedora (from a chroot into the fedora partition).
bash-completion and environment-modules are two ot
On 5/14/19 3:00 PM, Robert P. J. Day wrote:
i'm finally annoyed enough about this to just ask ... on a regular
basis, i mistype a command and (predictably) get:
bash: xxx: command not found...
but, quite often, rather than getting a bash prompt back immediately,
there is a lng pau
"Robert P. J. Day" writes:
> what in the name of mutt is bash doing all that time? if there's no
> such command, why the long pause in giving me a new prompt?
It's probably trying to give you a clue on how to install the right
package to get that command.
Try removing PackageKit-command-not-fo
pause after bash "command not found"?
>
> i'm finally annoyed enough about this to just ask ... on a regular
>basis, i mistype a command and (predictably) get:
>
> bash: xxx: command not found...
>
>but, quite often
==
i'm finally annoyed enough about this to just ask ... on a regular
basis, i mistype a command and (predictably) get:
bash: xxx: command not found...
but, quite often, rather than getting a bash prompt back immediately,
there is a lng pause, as i wait, and wait, and wait for a new
pro
On Sun, Jun 24, 2012 at 1:27 PM, Ed Greshko wrote:
> On 06/25/2012 12:55 AM, Richard Vickery wrote:
> > Bottom and top posting rules between posting here and the Developers
> list may get
> > confusing
>
> I'm sure you can handle it Does the Developer's list have rules about
> trimming
> unn
On 06/25/2012 12:55 AM, Richard Vickery wrote:
> Bottom and top posting rules between posting here and the Developers list may
> get
> confusing
I'm sure you can handle it Does the Developer's list have rules about
trimming
unnecessary cruft? :-) :-)
--
Never be afraid to laugh at yourse
On Fri, Jun 22, 2012 at 10:11 PM, Ed Greshko wrote:
> On 06/23/2012 12:19 PM, Richard Vickery wrote:
> > This is awesome Ed: Did it work like this before as well, and I was
> just ignorant
> > of it? Now all the commands are readable, which for me is better as it
> seemed as if
> > they were som
On 06/23/2012 12:19 PM, Richard Vickery wrote:
> This is awesome Ed: Did it work like this before as well, and I was just
> ignorant
> of it? Now all the commands are readable, which for me is better as it seemed
> as if
> they were somewhat jumbled, as the letter you are looking at seemed to me
This is awesome Ed: [?] Did it work like this before as well, and I was just
ignorant of it? Now all the commands are readable, which for me is better
as it seemed as if they were somewhat jumbled, as the letter you are
looking at seemed to meshed into the next.
Sorry that I didn't get to try the
On Fri, Jun 22, 2012 at 2:53 AM, Ed Greshko wrote:
> I'm taking a SWAG, but you'd probably have to edit
> /usr/share/bash-completion/bash_completion to get the old behavior back.
The OP can just wrap or redefine _minimal. Followed by a
$ complete -F # or _minimal if redefined
should do the job
On Thu, 2012-06-21 at 17:25 -0700, Richard Vickery wrote:
Hi gang:
>
>
> Before F-17 I had become accustomed through experience to using ,
hit twice, to get a full list of the commands; perhaps you set it by
default - at least in the release on the website. This time I upgraded
through the link
On 06/22/2012 08:25 AM, Richard Vickery wrote:
> Before F-17 I had become accustomed through experience to using , hit
> twice,
> to get a full list of the commands; perhaps you set it by default - at least
> in the
> release on the website. This time I upgraded through the link in the mail.
> P
On 6 June 2011 03:57, Rahul Sundaram wrote:
> It really isn't. It is just a workaround that produces inconsistent
> behaviour for reasons that are not clear or documented. The right fix
> would be to find out why yum doesn't work off the cache when told to and
> solve that problem but this worka
On 06/02/2011 05:19 PM, Chris Tyler wrote:
> On Thu, 2011-06-02 at 12:39 +0100, Richard Hughes wrote:
>>
>> This is by design. I lost count of the number of bugs opened against
>> PackageKit-command-not-found where yum would happily go and download
>> the latest metadata and take 3 minutes to ret
On Thu, 2011-06-02 at 16:09 +0200, Eric Tanguy wrote:
> Le 02/06/2011 15:30, Eric Tanguy a écrit :
> > Le 02/06/2011 13:12, Michael Schwendt a écrit :
> >> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
> >>
> >>> I tried uninstall and reinstall PackageKit-command-not-found with the
> >>> same resul
Le 02/06/2011 15:30, Eric Tanguy a écrit :
> Le 02/06/2011 13:12, Michael Schwendt a écrit :
>> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
>>
>>> I tried uninstall and reinstall PackageKit-command-not-found with the
>>> same result.
>>> Maybe a x86_64 problem ?
>> No. Don't just reinstall a pack
Le 02/06/2011 13:12, Michael Schwendt a écrit :
> On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
>
>> I tried uninstall and reinstall PackageKit-command-not-found with the
>> same result.
>> Maybe a x86_64 problem ?
> No. Don't just reinstall a package if it isn't broken.
> Try to examine the proble
On Thu, 2011-06-02 at 12:39 +0100, Richard Hughes wrote:
> On 2 June 2011 12:35, Chris Tyler wrote:
> > - If pk-c-n-f times out on fetching file list metadata, it seems to
> > silently stop trying to suggest packages. I've seen this on slow
> > connections and disconnected machines. IIRC, fetching
On 2 June 2011 12:35, Chris Tyler wrote:
> - If pk-c-n-f times out on fetching file list metadata, it seems to
> silently stop trying to suggest packages. I've seen this on slow
> connections and disconnected machines. IIRC, fetching recent metadata
> (e.g., by using yum to find a file-level depen
On Thu, 2011-06-02 at 11:43 +0200, Eric Tanguy wrote:
> I tried uninstall and reinstall PackageKit-command-not-found with the
> same result.
> Maybe a x86_64 problem ?
> Eric
>
Two observations:
- If Packagekit-command-not-found is active, the error message seems to
change from:
bash: thun
On Thu, 02 Jun 2011 11:43:19 +0200, ET wrote:
> I tried uninstall and reinstall PackageKit-command-not-found with the
> same result.
> Maybe a x86_64 problem ?
No. Don't just reinstall a package if it isn't broken.
Try to examine the problem a bit. Everything's there for
you to look at.
$ rpm -
Le 02/06/2011 11:36, Joachim Backes a écrit :
> On 06/02/2011 11:30 AM, Eric Tanguy wrote:
>> Le 02/06/2011 11:25, Joachim Backes a écrit :
>>> On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to
find
the package containing t
On 06/02/2011 11:30 AM, Eric Tanguy wrote:
Le 02/06/2011 11:25, Joachim Backes a écrit :
On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to find
the package containing this command.
This seems to not work in f15.
# telnet
bash: telnet:
Le 02/06/2011 11:25, Joachim Backes a écrit :
> On 06/02/2011 11:19 AM, Eric Tanguy wrote:
>> In fedora14 in cli if i try an unknown command the system tried to find
>> the package containing this command.
>> This seems to not work in f15.
>> # telnet
>> bash: telnet: command not found...
>>
>> and
On 06/02/2011 11:19 AM, Eric Tanguy wrote:
In fedora14 in cli if i try an unknown command the system tried to find
the package containing this command.
This seems to not work in f15.
# telnet
bash: telnet: command not found...
and that's all. The system does not propose to install telnet client
In fedora14 in cli if i try an unknown command the system tried to find
the package containing this command.
This seems to not work in f15.
# telnet
bash: telnet: command not found...
and that's all. The system does not propose to install telnet client
package.
Is this normal ?
Thanks
Eric
--
On 11/20/2010 08:15 PM, David Nelson wrote:
> Hi, :-)
>
> My bash command line on my FC12 VPS displays "[r...@example ~]#"
>
> How can I change it to "[r...@example.com ~]#"?
>
> TIA for any answers. :-)
>
>
http://tinyurl.com/2g7amrq
You did say &q
Hi, :-)
My bash command line on my FC12 VPS displays "[r...@example ~]#"
How can I change it to "[r...@example.com ~]#"?
TIA for any answers. :-)
David Nelson
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://adm
53 matches
Mail list logo
