Il giorno ven 1 mar 2019 alle ore 11:52 Mike Gran ha
scritto:
> On Mon, Feb 25, 2019 at 09:30:46AM +0100, Catonano wrote:
> > I added a test to the test-suite/tests/texinfo.serialize.test file,
> >
> > like this
> >
> > (assert-serialize '(defcodeindex (% (entry "op")))
> > "@defcod
Il giorno ven 1 mar 2019 alle ore 12:47 Mike Gran ha
scritto:
> On Sun, Feb 17, 2019 at 12:07:08PM +0300, Vladimir Zhbanov wrote:
> > Hi,
> >
> > Is there a way to not limit backtrace output with current terminal
> > width setting? When I compile my project which uses autotools and
> > srfi-64 te
API reference -> Debugging -> Programmatic error handling
Would you mind to let me know if you succeed in making this thing work for
you ?
Thanks
Is there a known issue for include-from-path for 2.0.14?
I'm testing install scripts and what seems to work with "guild" on 2.2.3
does not with 2.0.14:
context: foo.scm includes the expression (include-from-path
"abc/def/bar.scm")
On 2.2.3:
guild compile -L . -o abc/def/foo.go abc/def/fo
On 3/2/19 8:23 AM, Matt Wette wrote:
Is there a known issue for include-from-path for 2.0.14?
I'm testing install scripts and what seems to work with "guild" on
2.2.3 does not with 2.0.14:
context: foo.scm includes the expression (include-from-path
"abc/def/bar.scm")
On 2.2.3:
guild com
Il giorno sab 2 mar 2019 alle ore 17:03 Mike Gran ha
scritto:
> On Sat, Mar 02, 2019 at 04:23:34PM +0100, Catonano wrote:
> > API reference -> Debugging -> Programmatic error handling
> >
> > Would you mind to let me know if you succeed in making this thing work
> for
> > you ?
> >
> > Thanks
>
>
Hi simon,
Did you get to a workaround that works for you?
Best wishes,
Arne
Arne Babenhauserheide writes:
> Dear simon,
>
> Thank you for writing!
>
> The error-reporting in wisp is currently not at the level of regular
> Scheme. For some errors you already get the line numbers, but others
> s
