Re: does `pkill o` mean anything special ?

[Andreas Kähäri]

On Thu, Sep 12, 2024 at 09:39:41AM +0200, Kusalananda Kähäri wrote:
> On Thu, Sep 12, 2024 at 08:40:29AM +0200, alex xmb sw ratchev wrote:
> > oh , didnt know submatch is standard ..
> 
> It uses extended regular expressions (not shell globbing patterns), so
> you would have to anchor the pattern as you would do with any regular
> expression if you wish to match at the start or end of the string.  Or
> you can use pgrep/pkill with -x to match across the complete command
> line (as with "grep -x").

Correction: Use -x to match across the complete command *name*.  Use
-f to match the command *line* (with arguments).  Combine -f and -x to
match against the command line and to anchor the pattern at start and
stop.

Sorry for this off-topic side track.

> 
> > the process killed : com.termux
> > 
> > thanks , greets ..
> > 
> > On Thu, Sep 12, 2024, 8:30 AM Andreas Kähäri <andreas.kahari@abc.se> wrote:
> > 
> > > On Thu, Sep 12, 2024 at 07:50:53AM +0200, alex xmb sw ratchev wrote:
> > > > cause i stubled on accident over it
> > > > it kills the bash
> > > > at least , i enter pkill o ( small oo ) and press enter and then the 
> > > > bash
> > > > session got exited
> > > >
> > > > greets , microsuxx software ..
> > >
> > > This has absolutely nothing to do with bash, but pkill would send a TERM
> > > signal to all processes matching the given pattern.  If you want to have
> > > a hunch beforehand, use "pgrep -l" with the same pattern to see what it
> > > matches.
> > >
> > > Your pattern should match any running process that has a lower-case o in
> > > its name.
> > >
> > > --
> > > Andreas (Kusalananda) Kähäri
> > > Uppsala, Sweden
> > >
> > > .
> > >
> 
> -- 
> Andreas (Kusalananda) Kähäri
> Uppsala, Sweden
> 
> .

-- 
Andreas (Kusalananda) Kähäri
Uppsala, Sweden

.