bugGNU TeXmacs - Bugs: bug #63434, Setting a global scripting...


You are not allowed to post comments on this tracker with your current authentication level.

bug #63434: Setting a global scripting language preference interferes with executable folds

Submitter:  Jeroen Wouters <jeronim>
Submitted:  Mon 28 Nov 2022 11:43:25 AM UTC
Category:  Plugins Priority:  5 - Normal
Item Group:  Error Status:  Works For Me
Privacy:  Public Assigned to:  vdhoeven
Originator Name:  Open/Closed:  Open
Release:  None Release: 
Fixed Release:  None Fixed Release: 

Mon 07 Aug 2023 02:16:23 PM UTC, comment #1: 

I am unable to reproduce this bug (MacOS, Qt4).
I tried with several plug-ins.

You may try to debug the IO in order to see what is going on.

Joris van der Hoeven <vdhoeven>
Group administrator
Mon 28 Nov 2022 11:43:25 AM UTC, original submission:  

When setting a global scripting language preference in `Edit->Preferences->Other->Scripting language`, executable folds no longer  work.

1. Set `Edit->Preferences->Other->Scripting language` to `maxima` (though other languages seems to cause this as well. I tested maxima, python, and scheme)
2. Restart TeXmacs
3. Insert an executable fold `Insert->Fold->Executable->Python` (also here other folds give the same behaviour)
4. Enter some input, e.g. `1+1`
5. Activate the fold with Shift+Enter

The expected result is the output (e.g. 2) being inserted into the document. Nothing appears however.

Jeroen Wouters <jeronim>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by vdhoeven (Posted a comment)
  • -email is unavailable- added by jeronim (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-08-07 vdhoeven StatusNone Works For Me
        Assigned toNone vdhoeven

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code