unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Massimiliano Gubinelli <m.gubinelli@gmail.com>
To: guile-user@gnu.org
Subject: TeXmacs on Guile 2.2.4
Date: Sun, 26 May 2019 23:17:48 +0200	[thread overview]
Message-ID: <1D2A839C-66B5-4633-91B9-1C1ACFC306E7@gmail.com> (raw)

Hi all,

 I’m porting GNU TeXmacs (www.texmacs.org) to Guile 2.2.4 (and hopefully to Guile 3.0). The current status is the following. TeXmacs runs on Guile 2.2.4 with autocompilation turned off: the applications opens and can read and render some files. More work is necessary to switch on compilation. However I’ve a problem with reading some TeXmacs files from the disk. Some of them works OK, but others give errors while reading: the file is first read into a C string by TeXmacs and then converted into a SCM object for further manipulation by Guile. At that point I receive this error message

Backtrace:
           7 (apply-smob/1 #<catch-closure 117caea80>)
           6 (apply-smob/1 #<catch-closure 13de3dfc0>)
           5 (apply-smob/1 #<catch-closure 13de3df40>)
           4 (protected-call #<procedure 13de34380 at kernel/gui/men…>)
           3 (apply-smob/1 #<catch-closure 13de3dee0>)
           2 (apply-smob/1 #<catch-closure 13de3de80>)
In texmacs/texmacs/tm-files.scm:
   413:15  1 (load-buffer-load # ())
In unknown file:
           0 (buffer-load #)

ERROR: In procedure buffer-load:
Throw to key `decoding-error' with args `("scm_from_stringn" "input locale conversion error" 92 #vu8(60 84 101 88 109 97 99 115 124 49 46 57 57 46 57 62 10 10 60 115 116 121 108 101 124 60 116 117 112 108 101 124 97 114 116 105 99 108 101 124 98 114 105 116 105 115 104 124 99 111 109 112 97 99 116 45 108 105 115 116 62 62 10 10 60 92 98 111 100 121 62 10 32 32 60 92 104 105 100 101 45 112 114 101 97 109 98 108 101 62 10 32 32 32 32 92 59 10 10 32 32 32 32 60 97 115 115 105 103 110 124 98 105 98 108 105 111 103 114 97 112 104 121 45 116 101 120 116 124 60 109 97 99 114 111 124 60 108 111 99 97 108 105 122 101 124 66 105 98 108 105 111 103 114 97 112 104 [...cut here...]


Things works well with Guile 1.8, so I do not understand very well what is going on here. Somebody  has some clue as to what could cause this problem?

Thanks!

Masssimiliano Gubinelli

PS: I have the same problem on 2.9.2 (always with autocompilation off).








             reply	other threads:[~2019-05-26 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-26 21:17 Massimiliano Gubinelli [this message]
2019-05-26 23:49 ` TeXmacs on Guile 2.2.4 Mike Gran
2019-05-27 12:18   ` Massimiliano Gubinelli
2019-05-29 19:29     ` Mark H Weaver

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=1D2A839C-66B5-4633-91B9-1C1ACFC306E7@gmail.com \
    --to=m.gubinelli@gmail.com \
    --cc=guile-user@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).