From: "Wette, Matthew R (3441)" <matthew.r.wette@jpl.nasa.gov>
To: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: [FEATURE REQUEST] Add a hook to print warning message prefix string
Date: Fri, 18 Mar 2016 13:10:45 +0000 [thread overview]
Message-ID: <D4B9F9A5-2315-457D-896E-342DB20BA53A@jpl.nasa.gov> (raw)
In-Reply-To: <1458286708.3981.60.camel@Renee-desktop.suse>
> On Mar 18, 2016, at 12:38 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:
[…]
> So my suggestion is that we add a helper function to customize the
> warning message prefix string to make sure it's compatible for the
> specific language frontend.
>
> This feature is useful for our multi-lang plan in the future.
>
> Say, for Lua, like this:
>
> (set-warning-prefix! "---")
> ==============================start====================
> --- note: source file ./language/lua/stdlib/io.scm
> --- newer than
> compiled /home/nalaginrut/.cache/guile/ccache/2.2-LE-8-3.7/home/nalaginrut/Project/guile-lua-rebirth/language/lua/stdlib/io.scm.go
> --- note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> --- or pass the --no-auto-compile argument to disable.
> --- compiling ./language/lua/stdlib/io.scm
> ===============================end=====================
>
> What do you think?
What about a command line option to eliminate the message all together.
Matt
next prev parent reply other threads:[~2016-03-18 13:10 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) [this message]
2016-03-18 16:30 ` Nala Ginrut
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=D4B9F9A5-2315-457D-896E-342DB20BA53A@jpl.nasa.gov \
--to=matthew.r.wette@jpl.nasa.gov \
--cc=guile-devel@gnu.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).