unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: "Wette, Matthew R (3441)" <matthew.r.wette@jpl.nasa.gov>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: [FEATURE REQUEST] Add a hook to print warning message prefix string
Date: Sat, 19 Mar 2016 00:30:02 +0800	[thread overview]
Message-ID: <1458318602.3981.82.camel@Renee-desktop.suse> (raw)
In-Reply-To: <D4B9F9A5-2315-457D-896E-342DB20BA53A@jpl.nasa.gov>

On Fri, 2016-03-18 at 13:10 +0000, Wette, Matthew R (3441) wrote:
> What about a command line option to eliminate the message all together.
> 

That means each time the users want to use REPL to test Lua code, they
have to add an option to run Guile. IMO it's not the best solution. ;-)
But many thank for response!

Best regards.





      reply	other threads:[~2016-03-18 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  7:38 [FEATURE REQUEST] Add a hook to print warning message prefix string Nala Ginrut
2016-03-18 13:10 ` Wette, Matthew R (3441)
2016-03-18 16:30   ` Nala Ginrut [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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1458318602.3981.82.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=matthew.r.wette@jpl.nasa.gov \
    /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).