After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 658128 - Problem with the newline character in the script-fu console
Problem with the newline character in the script-fu console
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Script-Fu
git master
Other All
: Normal normal
: 2.10
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2011-09-03 15:46 UTC by florent53
Modified: 2016-11-17 00:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description florent53 2011-09-03 15:46:48 UTC
If we copy scheme code which contain newline characters in the console
this code is not well interpreted:

>'(1 2
3)
'(1 2)


> (define (test x)
    (print x)
)
#<EOF>

> (test 1)
Error: (<unknown> : 143167737) eval: unbound variable: test
Comment 1 Mukund Sivaraman 2011-09-21 15:18:42 UTC
Confirming.
Comment 2 Kevin Cozens 2011-09-22 15:45:07 UTC
In testing this report I used the '(1 2 3) list creation as shown by florent53.

When I compiled the version of TinyScheme from GIMP's source tree as a standalone program the example did yield a list with the expected three elements. The GUI console code passes the string to scheme_load_string() in TinyScheme. The strig (in hex) received by scheme_load_string() was "27 28 31 20 32 0A 33 29" as expected. This narrows the problem to how TinyScheme is reading data from a string buffer.
Comment 3 Ari Pollak 2013-01-29 01:34:16 UTC
http://bugs.debian.org/698847 seems to be related - this bug doesn't happen on amd64, but it does happen on i386.
Comment 4 Kevin Cozens 2014-02-03 22:54:04 UTC
The two examples work fine for me on a machine with an Intel CPU running 32-bit Linux. If this is specific to 64-bit Linux and an AMD processor I have no way to reproduce the problem unless someone feels like sending me an AMD based laptop I could use.
Comment 5 Michael Natterer 2016-11-16 16:54:15 UTC
I can't reproduce this, does this still happen to you?
Comment 6 Kevin Cozens 2016-11-16 20:44:01 UTC
Since I last commented on this bug my computer is now run with a 64-bit operating system. I haven't been able to reproduce this issue. Let's just close this report. It can be reopened if someone is able to reproduce the issue.
Comment 7 Michael Natterer 2016-11-17 00:42:56 UTC
Yeah, let's assume FIXED.