another excellent example why your posts are almost always worth reading.
thank you! :)
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
> Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> > The fact that this *appears* to work is what causes so much confusion.
> > It will "work" some of the time, but not all of the time, and you'll
> > get different results depending on which direc
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
[...]
> I was really curious, how Greg would put words to this one. And i gotta
> applaud: Such unambiguous explanations, and so circumspect at the same
> time. Even understanding the basis for confusion, i could learn
> something new from this
Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> The fact that this *appears* to work is what causes so much confusion.
> It will "work" some of the time, but not all of the time, and you'll
> get different results depending on which directory you're in, on which
> computer.
>
> Bash has two other
On Thu, Jan 19, 2023 at 07:13:46AM -0500, Greg Wooledge wrote:
[...]
> So, just to add to the list of people who've already said it: always
> quote the patterns that you pass to apt list, because you want apt
> to use them directly, without your shell interfering.
And, if in doubt, just replace
On Thu, Jan 19, 2023 at 12:11:43PM +0100, Christoph Brinkhaus wrote:
> For curiosity If have done a small test as below.
> Unfortunately there are a few outputs in German. For this comparisons
> the exact meanings of the German text has no importance at all.
>
> 1. The first command of the origina
Am Thu, Jan 19, 2023 at 11:40:50AM +0100 schrieb to...@tuxteam.de:
Hello Tomas,
> On Thu, Jan 19, 2023 at 11:31:23AM +0100, Christoph Brinkhaus wrote:
> > Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
> >
> > Hello Julian,
> >
> > > Hello together,
> > > listing packages i
On Thu, Jan 19, 2023 at 11:31:23AM +0100, Christoph Brinkhaus wrote:
> Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
>
> Hello Julian,
>
> > Hello together,
> > listing packages in apt with ”sudo“ in the title returns different output
> > (bash commands at the end of the em
Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
Hello Julian,
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to address it to grep
19.01.23, 09:10 +0100, js-p...@online.de:
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
To me it seems t
Am 19.01.2023 um 09:10 schrieb js-p...@online.de:
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to address it to grep or apt. How do you see this?
>
>
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
Kind regards
Julian Schreck
--
$ apt list sudo* vs. $ apt l
12 matches
Mail list logo
