Christopher wrote on Fri, May 24, 2024 at 02:15:17AM -0400:
> A flag to treat the arguments as OR like mlocate did instead of the default
> to AND would be great, though I wish plocate would have more closely
> mimicked mlocate's default behavior from the beginning and had a flag for
> AND
Christopher wrote on Fri, May 24, 2024 at 02:18:04AM -0400:
> Are you sure you have the correct address for the plocate developer and
> that it's still actively maintained? I just got an error that the
> destination email address didn't exist from their mail server when I
> replied just now.
Are you sure you have the correct address for the plocate developer and
that it's still actively maintained? I just got an error that the
destination email address didn't exist from their mail server when I
replied just now.
On Fri, May 24, 2024, 02:15 Christopher wrote:
> A flag to treat the
A flag to treat the arguments as OR like mlocate did instead of the default
to AND would be great, though I wish plocate would have more closely
mimicked mlocate's default behavior from the beginning and had a flag for
AND instead. Unfortunately, one cannot go back in time.
On Thu, May 23, 2024,
Christopher wrote on Thu, May 23, 2024 at 06:26:57PM -0400:
> One thing I've noticed is that plocate behaves differently when
> supplied with multiple arguments than mlocate. This broke some of my
> scripts.
>
> Previously, I had:
>
> locate rpm{old,new,save,orig,moved}
> # expands to
One thing I've noticed is that plocate behaves differently when
supplied with multiple arguments than mlocate. This broke some of my
scripts.
Previously, I had:
locate rpm{old,new,save,orig,moved}
# expands to locate rpmold rpmnew rpmsave rpmorig rpmmoved
But now, I need to do:
for
On Tue, May 21, 2024 at 01:19:24PM +0200, Miro Hrončok wrote:
> On 21. 05. 24 12:29, Fabio Valentini wrote:
> > On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote:
> > >
> > > On Fri, May 17, 2024 at 6:14 PM Michal Sekletar
> > > wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > We have
On 21. 05. 24 12:29, Fabio Valentini wrote:
On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote:
On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote:
Hi everyone,
We have had a plocate as a drop-in replacement for mlocate for quite a while
now. My intention is to retire the mlocate
On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote:
>
> On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote:
>>
>> Hi everyone,
>>
>> We have had a plocate as a drop-in replacement for mlocate for quite a while
>> now. My intention is to retire the mlocate package next week in order to
>>
On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote:
> Hi everyone,
>
> We have had a plocate as a drop-in replacement for mlocate for quite a
> while now. My intention is to retire the mlocate package next week in order
> to prevent duplication and so that we can focus only on plocate
> going
Hi everyone,
We have had a plocate as a drop-in replacement for mlocate for quite a
while now. My intention is to retire the mlocate package next week in order
to prevent duplication and so that we can focus only on plocate
going forward.
Have a nice weekend,
Michal
--
11 matches
Mail list logo
