cm_puts (" compiled ", scm_current_warning_port ());
+ scm_display (res, scm_current_warning_port ());
+ scm_newline (scm_current_warning_port ());
+ }
return res;
}
else
@@ -1349,6 +1358,8 @@ scm_init_load ()
= SCM_VARIABLE_LOC (scm_c_define (&qu
Hi :)
On Wed 20 Jul 2016 08:41, Tobin Harding writes:
> On Thu, Jul 14, 2016 at 12:01:10PM +0200, Andy Wingo wrote:
>> On Wed 13 Jul 2016 06:08, Tobin Harding writes:
>>
>> > While working on this I discovered that compile messages are output from
>> > two
>> > separate places (load.c and boo
entries (referencing doc/) in .gitignore are
/doc/ref/standard-library.texi
/doc/ref/standard-libraryscmfiles
The docs came down with git clone so obviously they are known to git somehow?
I roughed up a document addition, is this the sort of thing you would like
-- Scheme Variable: %verbose-
@ do_try_auto_compile (void *data)
/* Assume `*current-warning-prefix*' has an appropriate value. */
res = scm_call_n (scm_variable_ref (compile_file), args, 5);
- scm_puts (" compiled ", scm_current_warning_port ());
- scm_display (res, scm_current_warning_p
Hi :)
Thanks for the patch!
On Wed 13 Jul 2016 06:08, Tobin Harding writes:
> While working on this I discovered that compile messages are output from two
> separate places (load.c and boot-9.scm). Each file contains identical strings
> for the messages. This goes against the rule of SPOT.
Sad
Patch adds command line option '--quiet' to inhibit compile and load messages.
---
This is version 2. Submitting this patch on a new email thread.
While working on this I discovered that compile messages are output from two
separate places (load.c and boot-9.scm). Each file contains identical st
On Tue 12 Jul 2016 02:08, Tobin Harding writes:
> On Mon, Jul 11, 2016 at 06:29:43PM +0200, Andy Wingo wrote:
>> On Thu 07 Jul 2016 14:52, Tobin Harding writes:
>>
>> > I have two issues with this patch after developing with a patched Guile
>> > for a
>> > week or so. First is that I have not
On Mon, Jul 11, 2016 at 06:29:43PM +0200, Andy Wingo wrote:
> On Thu 07 Jul 2016 14:52, Tobin Harding writes:
>
> > I have two issues with this patch after developing with a patched Guile for
> > a
> > week or so. First is that I have not been able to pass command line options
> > to
> > Guile
On Thu 07 Jul 2016 14:52, Tobin Harding writes:
> I have two issues with this patch after developing with a patched Guile for a
> week or so. First is that I have not been able to pass command line options to
> Guile while using Geiser, my workaround has been setting the variable
> %quiet-compile
ption name as I originally wrote it, not to ignore you Andy but
simply to get any other feed back on the patch then I will re-submit it.
The option --with-compiler-messages is redundant (since its the default
behaviour). I added it to be inline with --auto-compile/--no-auto-compile.
I have two is
On Thu 30 Jun 2016 12:57, Tobin Harding writes:
> Request for advice as to whether to submit patch?
Sure, please do. I guess --quiet is the name that is most often asked
for.
Andy
/2011-03/msg00079.html
Patch adds command line option --without-compiler-messages. This option inhibits
the messages
;;; note: source file /home/tobin/build/scheme/test.scm
;;; newer than compiled
/home/tobin/.cache/guile/ccache/2.2-LE-8-3.8/home/tobin/build/scheme/test.scm.go
;;; compiling
12 matches
Mail list logo
