bugGNU TeXmacs - Bugs: bug #64562, xmacro's with arity greater than...


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

bug #64562: xmacro's with arity greater than 64 drop arguments

Submitter:  Jeroen Wouters <jeronim>
Submitted:  Wed 16 Aug 2023 12:58:13 PM UTC
Category:  Styles Priority:  3 - Low
Item Group:  Error Status:  Postponed
Privacy:  Public Assigned to:  vdhoeven
Originator Name:  Open/Closed:  Open
Release:  None Release: 
Fixed Release:  None Fixed Release: 
Keywords:  xmacro

Fri 27 Oct 2023 06:02:28 PM UTC, comment #3: 

Thanks. I was trying to make an editable 8x8 chessboard macro when I stumbled onto this.

Jeroen Wouters <jeronim>
Group Member
Fri 27 Oct 2023 04:20:10 PM UTC, comment #2: 

Yes, the arity is limited to <= 63 for the moment; this should have been documented so far.  We might easily increase the limit on 64 bit architectures, but 32 bit machines seem still to be used for the moment.

Out of curiosity, for what do you need larger arities?

Joris van der Hoeven <vdhoeven>
Group administrator
Wed 16 Aug 2023 02:08:58 PM UTC, comment #1: 

This seems to arise from `tag_info.cpp` where `arity_base` is determined via `get_bits (arity_base      , 6);`.

Jeroen Wouters <jeronim>
Group Member
Wed 16 Aug 2023 12:58:13 PM UTC, original submission:  

The following macro results in a macro with only two editable fields in the editor:

<assign|tobold|<macro|x| - <with|font-series|bold|<arg|x>> >>



A similar thing happens with arity set to 130. The resulting arity seems to be modulo 64.

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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-10-27 vdhoeven CategoryNone Styles
    2023-10-27 vdhoeven Assigned toNone vdhoeven
    2023-10-27 vdhoeven Priority5 - Normal 3 - Low
        StatusNone Postponed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code