From: Wojtek Kosior via <help-guix@gnu.org>
To: Gottfried <gottfried@posteo.de>
Cc: Martin Castillo <castilma@uni-bremen.de>, help-guix@gnu.org
Subject: Re: creating a manifest
Date: Mon, 27 Mar 2023 20:06:01 +0200 [thread overview]
Message-ID: <20230327200601.350338b7.koszko@koszko.org> (raw)
In-Reply-To: <b7192a31-6b02-eca3-5878-82b16f072355@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 3979 bytes --]
> and there are loads of messages:
> > gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil
> > gfp@Tuxedo ~ [env]$ mscore &
> > [1] 5761
> > gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > ScoreFont::draw: invalid sym 0
>
> I don’t know what to do with them.
It's quite common that GUI applications produce quite a lot of text
output when run from the command line. You can get rid of that text by
replacing lines like
command-name &
with lines like
command-name >/dev/null 2>/dev/null &
This redirects the *standard output* and *standard error output* of the
new process to your system's local black hole. Additionally, if you
don't want the processes started with "&" to be killed when you close
the terminal window, you can use the "disown" shell builtin after
spawning each process. So, in your terminal you could now write
command-name >/dev/null 2>/dev/null &
disown
You can also make it a bit shorter at the cost of adding a bit more
complexity. Feel free to ignore this option and its explanation if it
seems like too much of a black magic. So, you'd write in one line
command-name >/dev/null 2>&1 & disown
The second occurrence of "/dev/null" got replaced with "&1" which is a
reference to already-assigned standard output destination. And the
newline before "disown" was removed because the shell already knows the
stuff after "&" is a separate command
Wojtek
-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
On Mon, 27 Mar 2023 11:52:20 +0000
Gottfried <gottfried@posteo.de> wrote:
> and there are loads of messages:
> > gfp@Tuxedo ~$ guix shell -p ~/Projekte/Musik/guix-profil
> > gfp@Tuxedo ~ [env]$ mscore &
> > [1] 5761
> > gfp@Tuxedo ~ [env]$ ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > ZoomBox::setLogicalZoom(): Formatting logical zoom level as 100% (rounded from 1.000000)
> > qrc:/qml/palettes/PaletteTree.qml:772:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > qrc:/qml/palettes/Palette.qml:766:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
> > ScoreFont::draw: invalid sym 0
>
> I don’t know what to do with them.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-03-27 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 10:50 creating a manifest Gottfried
2023-03-18 11:48 ` Martin Castillo
2023-03-18 12:44 ` Martin Castillo
2023-03-18 18:58 ` Gottfried
[not found] ` <DFF79ED1-D430-4DE9-81C9-C1B146E1B84D@uni-bremen.de>
[not found] ` <ddb1213e-3864-bbdc-381d-aed8f9f4ace2@posteo.de>
[not found] ` <400c34f4-61e4-fc2e-f826-8b6d2c37f62b@uni-bremen.de>
[not found] ` <726a7642-df0b-495b-4b24-ce956533cba7@posteo.de>
[not found] ` <81AEB7B8-17C7-4484-90B6-BFEF5163B670@uni-bremen.de>
2023-03-25 12:49 ` Gottfried
2023-03-25 22:07 ` Martin Castillo
2023-03-26 8:16 ` Gottfried
2023-03-26 11:36 ` Martin Castillo
2023-03-26 13:07 ` Gottfried
2023-03-26 18:36 ` Martin Castillo
2023-03-27 11:52 ` Gottfried
2023-03-27 18:06 ` Wojtek Kosior via [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230327200601.350338b7.koszko@koszko.org \
--to=help-guix@gnu.org \
--cc=castilma@uni-bremen.de \
--cc=gottfried@posteo.de \
--cc=koszko@koszko.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.
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).