From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44118@debbugs.gnu.org
Subject: bug#44118: 28.0.50; Unwanted switch of foreground colour in *shell* buffer
Date: Sat, 12 Dec 2020 12:12:14 +0100 [thread overview]
Message-ID: <6CFCACEF-2A1E-4074-B615-C6A74BB718BC@Web.DE> (raw)
In-Reply-To: <87o8iz70rf.fsf@gnus.org>
> Am 12.12.2020 um 11:54 schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> What's the command you're running in shell mode when this happens, exactly?
port upgrade asciidoc cmake djvulibre
This upgrades in my present situation
asciidoc @9.0.3_0, cmake @3.19.1_0+docs+python38, djvulibre @3.5.27_0 to versions
asciidoc @9.0.4_0, cmake @3.19.1_1+docs+python38, djvulibre @3.5.28_0
and also includes upgrading of
libarchive @3.5.0_0, py38-pygments @2.7.2_0, py38-tz @2020.1_0 to versions
libarchive @3.5.0_1, py38-pygments @2.7.3_0, py38-tz @2020.4_0 since some dependencies there exist. And since some other ports might depend on the newly installed binaries the MacPorts system is being scanned for these. During this you might be able to see progress bars appear. After this stage the colour is switched.
--
Greetings
Pete
Swimming in money is dry fun.
next prev parent reply other threads:[~2020-12-12 11:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 18:10 bug#44118: 28.0.50; Unwanted switch of foreground colour in *shell* buffer Peter Dyballa
2020-12-09 13:24 ` Lars Ingebrigtsen
2020-12-09 13:44 ` Peter Dyballa
2020-12-10 14:09 ` Peter Dyballa
2020-12-11 14:47 ` Lars Ingebrigtsen
2020-12-11 15:23 ` Peter Dyballa
2020-12-11 15:27 ` Lars Ingebrigtsen
2020-12-11 16:30 ` Peter Dyballa
2020-12-12 10:54 ` Lars Ingebrigtsen
2020-12-12 11:12 ` Peter Dyballa [this message]
2020-12-18 23:18 ` Lars Ingebrigtsen
2020-12-19 9:53 ` Peter Dyballa
2020-12-19 15:48 ` Lars Ingebrigtsen
2021-02-22 16:12 ` Lars Ingebrigtsen
2021-02-22 20:03 ` Peter Dyballa
2021-02-22 21:16 ` Peter Dyballa
2021-02-22 21:41 ` Lars Ingebrigtsen
2022-03-21 22:15 ` Lars Ingebrigtsen
2020-12-10 14:58 ` Peter Dyballa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6CFCACEF-2A1E-4074-B615-C6A74BB718BC@Web.DE \
--to=peter_dyballa@web.de \
--cc=44118@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).