bugGNU TeXmacs - Bugs: bug #62800, Allow specific tag to have...

 
 

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

bug #62800: Allow specific tag to have multiline contents

Submitter:  Gennady Uraltsev <guraltsev>
Submitted:  Fri 22 Jul 2022 06:53:14 PM UTC
 
Category:  Editor Priority:  5 - Normal
Item Group:  Wishlist Status:  None
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  None Release: 
Fixed Release:  None Fixed Release: 
Keywords: 

Sat 05 Nov 2022 01:26:48 PM UTC, comment #1: 

This is also used when one uses TikZ/LaTeX executative plugins, say, since these codes are LaTeX codes, it is natural to keep them in the converted LaTeX code, and a hacking is using <specific|texmacs|...> to include the TeXmacs code for the plugin, say, <script-output ...>, and <specific|latex|...> to include the TikZ/LaTeX code.

I want to point out that there is a workaround, although not perfect: use the text editor (instead of TeXmacs) to insert multi-line codes in the <specific|...|...>, and reload it through TeXmacs.

Aeh9quu9 <ohnie0ai>
Fri 22 Jul 2022 06:53:14 PM UTC, original submission:  

One of the intended uses of the =specific= tag is to include code that will be exported only to latex into the preamble.

It would be nice to be able to include multiline content into the tag. Currently, this is not possible.

Here is a usecase:

I define several macros in the preamble that I use consistently in TeXmacs in a given paper (recurring operators/constructions). My workflow would require the following:

1) Ask Texmacs not to include any of the macro definitions into the latex file and just use the macros as is.
2) Ask Texmacs to include handwritten macro definitions into the latex file.

1 & 2 require to surround every TeXmacs =assign= command in the preamble by a =<specific|texmacs|???>= tag.

2 requires writing TeX code and surrounding each line by the =<specific|latex|???>= tag

2alt) write all latex code into a separate file e.g. =paper.sty= kept in the same directory + add one directive:
=<specific|latex|\usepackage{paper}>=

Note that 2alt still requires surrounding every texmacs assign statement with a =<specific|texmacs|???>= tag.

I know that defining a texmacs style is a more proper way, however

- it is more technically involved

- Texmacs has bugs when dealing with per-project styles that are included locally, rather than including globally installed ones. (on Windows)

The ability to surround a large block with =<specific|texmacs|???>= would be a fantastic intermediate solution.

Gennady Uraltsev <guraltsev>

 

(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 ohnie0ai (Posted a comment)
  • -email is unavailable- added by guraltsev (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.

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9