TZUTC: -0700   
   MSGID: 55066.sync@1:103/705 2d5e7efa   
   REPLY: 55064.sync@1:103/705 2d5e2a2c   
   PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: How do you edit msg files   
     By: Mindsurfer to Digital Man on Wed Oct 22 2025 01:43 am   
      
    >   Re: How do you edit msg files   
    >   By: Digital Man to Mindsurfer on Tue Oct 21 2025 15:06:24   
    >   
    >  >> Currently i am using Moebius for Linux to edit the ANS files. There is   
    >  >> IcyDraw, wich can handle MSG files directly (i guess), but it always is   
    > no   
    >  >> WYSIWYG editing as soon as you want to use @Codes, but guessing,   
    > measuring,   
    >  >> textediting afterwards.   
    >  >> Example: head.msg/head.ans IcyDraw/Moebius https://imgur.com/a/T9anJRs   
    >   
    >  DM> One thing that helps is insuring that the raw @-code uses the same   
    >  DM> number of characters as the fixed/maximum length of the displayed   
    >  DM> string using fill characters (e.g. #'s) see   
    >  DM> https://wiki.synchro.net/custom:atcodes#formatting for an exmaple.   
    >   
    > Ok. i am using something like that already, for shortening the Time   
    > (AT)TIME-L5(AT) for example. I was reading about the formatting features and   
    > will use em. the @CODE|R#######@ could also come in handy for longer   
    > strings.   
    >   
    >  DM> This works so long as the width of the string is less than or equal to   
    >  DM> the total length of the raw @-code. If you find an @-code where you'd   
    >  DM> prefer a shorter alternative alias, let me know and I'll see what I can   
    >  DM> do for ya.   
    >   
    > Thanks for the alternative short-code offer!   
    > I guess editing the ansi WYSIWYG when using @codes can work in some cases   
    > but is limited.   
    >   
    > The only thing that comes to my mind as a workaround, is to use placeholders   
    > with the correct length and a script to replace the placeholders with the   
    > @codes in the ANS file afterwards. for example ~~~1 ~~~~~~~~2 ~3 as   
    > placeholders, to be replaced with the @code-l4@ (~~~1) etc.   
      
   So what I was suggesting was that the @-code itself can be the "placeholder"   
   (so long as the @-code is the same length as the expanded string).   
   --    
                                               digital man (rob)   
      
   Sling Blade quote #10:   
   Morris: I stand on the hill, not for thrill, but for the breath of a fresh kill   
   Norco, CA WX: 63.6øF, 81.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.30-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880   
   SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426