From: Benno Schulenberg <benno.schulenberg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bad nano RESOLVED
Date: Tue, 26 Sep 2006 22:49:10 +0200 [thread overview]
Message-ID: <200609262249.10305.benno.schulenberg@gmail.com> (raw)
In-Reply-To: <20060926195027.4347.qmail@web31705.mail.mud.yahoo.com>
maxim wexler wrote:
> > Remove the debug USE flag from your /etc/make.conf.
>
> Awsome! May I ask how you knew this?
Those strange outputs have been posted before.
> What is the connection between the debug
> flag and strange nano behaviour?
What "debug" in most other ebuilds does I don't know, but in nano it
switches on all those print statements. Normally you would then
redirect error output to a file, 'nano somefile 2>debugoutput', so
you don't get those lines dumped to the screen.
Benno
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-09-26 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 15:51 [gentoo-user] bad nano maxim wexler
2006-09-26 16:32 ` Benno Schulenberg
2006-09-26 19:50 ` [gentoo-user] bad nanoRESOLVED maxim wexler
2006-09-26 20:49 ` Benno Schulenberg [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609262249.10305.benno.schulenberg@gmail.com \
--to=benno.schulenberg@gmail.com \
--cc=gentoo-user@lists.gentoo.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