https://lists.debian.org/debian-user/2017/08/msg00425.html
Felix Miata composed on 2017-08-08 14:05 (UTC-0500):
> Brian composed on 2017-08-08 13:49 (UTC+0100):
>> Apologies. I missed off a ";" when translating the changelog entry to
>> be used in your 99mono file. Also Progress-Fancy turns out
On Wed 09 Aug 2017 at 13:20:26 -0400, Greg Wooledge wrote:
> On Wed, Aug 09, 2017 at 06:12:31PM +0100, Brian wrote:
> > On Tue 08 Aug 2017 at 14:05:10 -0400, Felix Miata wrote:
> > > >From what documentation did Curt and you determine Apt::Color was the
> > > >solution?
> > > Google turns up "Apt
On Wed, Aug 09, 2017 at 06:12:31PM +0100, Brian wrote:
> On Tue 08 Aug 2017 at 14:05:10 -0400, Felix Miata wrote:
> > >From what documentation did Curt and you determine Apt::Color was the
> > >solution?
> > Google turns up "Apt::Color "false";" or "Apt::Color 0" nowhere except in
> > this
> > th
On Tue 08 Aug 2017 at 14:05:10 -0400, Felix Miata wrote:
> Brian composed on 2017-08-08 13:49 (UTC+0100):
>
> > Apologies. I missed off a ";" when translating the changelog entry to
> > be used in your 99mono file. Also Progress-Fancy turns out to be not
> > what you want.
>
> > "-o Apt::Color=0
Brian composed on 2017-08-08 13:49 (UTC+0100):
> Apologies. I missed off a ";" when translating the changelog entry to
> be used in your 99mono file. Also Progress-Fancy turns out to be not
> what you want.
> "-o Apt::Color=0" works for me not to see the orange colour in stable
> and unstable. In
On Tue 08 Aug 2017 at 05:32:04 -0400, Felix Miata wrote:
> Frank composed on 2017-08-08 10:31 (UTC+0200):
>
> > Felix Miata composed:
>
> >> Brian composed on 2017-08-07 33:42 (UTC+0100):
>
> >>> Of course they work. They just do not fit your purpose.
>
> >> Work how? Do what? How do I find ev
Curt composed on 2017-08-08 08:17 (UTC):
> On 2017-08-07, Felix Miata wrote:
>>> Try "APT::Color "false";".
>> That was the last I tried with Stretch before giving up and posting here, in
>> /etc/apt/apt.conf.d/99mono. Also fails in Sid.
>> Could this somehow be coming from bash rather than apt?
Frank composed on 2017-08-08 10:31 (UTC+0200):
> Felix Miata composed:
>> Brian composed on 2017-08-07 33:42 (UTC+0100):
>>> Of course they work. They just do not fit your purpose.
>> Work how? Do what? How do I find evidence that either actually do anything?
>> So
>> far all I've seen is that
Op 08-08-17 om 02:57 schreef Felix Miata:
Brian composed on 2017-08-07 33:42 (UTC+0100):
Of course they work. They just do not fit your purpose.
Work how? Do what? How do I find evidence that either actually do anything? So
far all I've seen is that you've said so, here, & earlier, 2017-08-07
On 2017-08-07, Felix Miata wrote:
>
>> Try "APT::Color "false";".
> That was the last I tried with Stretch before giving up and posting here, in
> /etc/apt/apt.conf.d/99mono. Also fails in Sid.
>
> Could this somehow be coming from bash rather than apt?
Did you try first at the command line?
ap
On 07.08.17 11:26, Greg Wooledge wrote:
> I don't understand; what part seems odd? My use of terminals with
> white backgrounds? That's fair. Most Linux kids these days seem to
> prefer black backgrounds.
For the last 30 odd years I've used yellow and green on DarkSlateGrey
for everything I can
Brian composed on 2017-08-07 33:42 (UTC+0100):
> On Mon 07 Aug 2017 at 15:02:28 -0400, Felix Miata wrote:
>> Brian composed on 2017-08-07 13:33 (UTC+0100):
>> > On Mon 07 Aug 2017 at 08:05:28 -0400, Felix Miata wrote:
>> >> Darac Marjal composed on 2017-08-07 11:20 (UTC+0100):
>> ...
>> >> > Tr
Greg Wooledge composed on 2017-08-07 09:13 (UTC-0400):
>> > > I didn't even know apt did colors. Can you give an example?
>> Ahem... is there also something non-destructive? ;-)
> apt search mariadb-server
> The package names are written in green (at least in my terminal).
Almost same here. 'a
On Mon 07 Aug 2017 at 15:02:28 -0400, Felix Miata wrote:
> Brian composed on 2017-08-07 13:33 (UTC+0100):
>
> > On Mon 07 Aug 2017 at 08:05:28 -0400, Felix Miata wrote:
>
> >> Darac Marjal composed on 2017-08-07 11:20 (UTC+0100):
> ...
> >> > Try "APT::Color "false";".
> >> That was the last I t
On Mon, Aug 07, 2017 at 04:14:28PM -0400, Gene Heskett wrote:
> On Monday 07 August 2017 11:26:16 Greg Wooledge wrote:
> > Or do you dispute the fact that apt uses yellow foreground text when
> > you do "apt update"?
>
> I see the link namestring and path in a medium red while its fetching the
>
On Monday 07 August 2017 11:26:16 Greg Wooledge wrote:
> On Mon, Aug 07, 2017 at 11:02:10AM -0400, Gene Heskett wrote:
> > On Monday 07 August 2017 08:39:46 Greg Wooledge wrote:
> > > Also while I'm here: the garish colors of apt(8) are not the #1
> > > reason I switched back to apt-get(8), but th
Brian composed on 2017-08-07 13:33 (UTC+0100):
> On Mon 07 Aug 2017 at 08:05:28 -0400, Felix Miata wrote:
>> Darac Marjal composed on 2017-08-07 11:20 (UTC+0100):
...
>> > Try "APT::Color "false";".
>> That was the last I tried with Stretch before giving up and posting here, in
>> /etc/apt/apt.co
On Mon 07 Aug 2017 at 15:10:45 +0200, to...@tuxteam.de wrote:
> On Mon, Aug 07, 2017 at 01:33:20PM +0100, Brian wrote:
>
> [...]
>
> > Worth reading: /usr/share/doc/apt/examples/configure-index.gz
> >
> > Try: Dpkg::Progress-Fancy::progress-bg "%1b[40m"
>
> Yikes. Another one reinventing termi
On Mon, Aug 07, 2017 at 11:02:10AM -0400, Gene Heskett wrote:
> On Monday 07 August 2017 08:39:46 Greg Wooledge wrote:
> > Also while I'm here: the garish colors of apt(8) are not the #1 reason
> > I switched back to apt-get(8), but they are #2. Whoever chose the
> > colors clearly doesn't use a t
On Monday 07 August 2017 09:13:42 Greg Wooledge wrote:
> On Mon, Aug 07, 2017 at 03:08:59PM +0200, to...@tuxteam.de wrote:
> > > > I didn't even know apt did colors. Can you give an example?
> >
> > Ahem... is there also something non-destructive? ;-)
>
> apt search mariadb-server
>
> The package
On Monday 07 August 2017 08:39:46 Greg Wooledge wrote:
> On Mon, Aug 07, 2017 at 08:05:28AM -0400, Felix Miata wrote:
> > Could this somehow be coming from bash rather than apt?
>
> Nope.
>
> Also while I'm here: the garish colors of apt(8) are not the #1 reason
> I switched back to apt-get(8), bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 07, 2017 at 09:13:42AM -0400, Greg Wooledge wrote:
> On Mon, Aug 07, 2017 at 03:08:59PM +0200, to...@tuxteam.de wrote:
> > > > I didn't even know apt did colors. Can you give an example?
> >
> > Ahem... is there also something non-destruct
On Mon, Aug 07, 2017 at 03:08:59PM +0200, to...@tuxteam.de wrote:
> > > I didn't even know apt did colors. Can you give an example?
>
> Ahem... is there also something non-destructive? ;-)
apt search mariadb-server
The package names are written in green (at least in my terminal).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 07, 2017 at 01:33:20PM +0100, Brian wrote:
[...]
> Worth reading: /usr/share/doc/apt/examples/configure-index.gz
>
> Try: Dpkg::Progress-Fancy::progress-bg "%1b[40m"
Yikes. Another one reinventing terminfo instead of relying on it.
Tho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 07, 2017 at 07:52:18AM -0400, Felix Miata wrote:
> to...@tuxteam.de composed on 2017-08-07 11:26 (UTC+0200):
>
> > I didn't even know apt did colors. Can you give an example?
>
> apt update
>
> apt upgrade
Ahem... is there a
On Mon, Aug 07, 2017 at 08:05:28AM -0400, Felix Miata wrote:
> Could this somehow be coming from bash rather than apt?
Nope.
Also while I'm here: the garish colors of apt(8) are not the #1 reason
I switched back to apt-get(8), but they are #2. Whoever chose the colors
clearly doesn't use a termi
On Mon 07 Aug 2017 at 08:05:28 -0400, Felix Miata wrote:
> Darac Marjal composed on 2017-08-07 11:20 (UTC+0100):
>
> > On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
>
> >>Google and man pages for apt, apt-config and apt.conf have gotten me
> >>nowhere in
> >>over an hour of searc
Darac Marjal composed on 2017-08-07 11:20 (UTC+0100):
> On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
>>Google and man pages for apt, apt-config and apt.conf have gotten me nowhere
>>in
>>over an hour of searching how to keep apt output limited to the two screen
>>colors in which
to...@tuxteam.de composed on 2017-08-07 11:26 (UTC+0200):
> I didn't even know apt did colors. Can you give an example?
apt update
apt upgrade
With both, portions of progress reporting use orange or green as foreground
color, depending on what's progressing.
--
"The wise are kn
On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
Google and man pages for apt, apt-config and apt.conf have gotten me nowhere in
over an hour of searching how to keep apt output limited to the two screen
colors in which it is running. Something like
Apt::what-goes "here";
ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 07, 2017 at 04:47:08AM -0400, Felix Miata wrote:
> to...@tuxteam.de composed on 2017-08-07 10:25 (UTC+0200):
>
> > On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
>
> >> Google and man pages for apt, apt-config and apt.conf h
to...@tuxteam.de composed on 2017-08-07 10:25 (UTC+0200):
> On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
>> Google and man pages for apt, apt-config and apt.conf have gotten me nowhere
>> in
>> over an hour of searching how to keep apt output limited to the two screen
>> colors i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Aug 07, 2017 at 04:16:05AM -0400, Felix Miata wrote:
> Google and man pages for apt, apt-config and apt.conf have gotten me nowhere
> in
> over an hour of searching how to keep apt output limited to the two screen
> colors in which it is runni
Google and man pages for apt, apt-config and apt.conf have gotten me nowhere in
over an hour of searching how to keep apt output limited to the two screen
colors in which it is running. Something like
Apt::what-goes "here";
ought to do it in some file in /etc/apt/apt.conf.d/, but by what
34 matches
Mail list logo
