| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 161.1 | Use EDT as you editor type within ALL-IN-1 | GIDDAY::SETHI | Man from Downunder | Wed Mar 04 1992 00:38 | 9 | 
|  |     Hi Gene,
    
    I have done this in the past by selecting EDT as my editor.  Then I
    have used <ESC> codes to set the characteristics for the text I can not
    remember what the <ESC> codes are.
    
    I hope it helps
    
    Sunil
 | 
| 161.2 | small table | UTRTSC::BOSMAN | We're just sugar mice in the rain | Wed Mar 04 1992 08:36 | 14 | 
|  |     Hi,
    
     attribute     on        off
    -----------------------------------
     bold       |  <ESC>[1m  <ESC>[22m
     underline  |  <ESC>[4m  <ESC>[24m
     blink      |  <ESC>[5m  <ESC>[25m
     highlight  |  <ESC>[7m  <ESC>[27m
     all attr.  |            <ESC>[0m
    -----------------------------------
    
    Instead of <ESC>[ you could also use <CSI> (ASCII 155).
    
    Sjaak.
 | 
| 161.3 | Nit-picking... | SCOTTC::MARSHALL | Pearl-white, but slightly shop-soiled | Wed Mar 04 1992 10:37 | 6 | 
|  | >> Instead of <ESC>[ you could also use <CSI> (ASCII 155).
But this won't work if the receiving terminal is in 7-bit mode, or is connected
to a 7-bit line, or if any line between sender and recipient is 7 bits.
Scott
 | 
| 161.4 | Not any more, I'm afraid | IOSG::SHOVE | Dave Shove -- REO-D/3C | Thu Mar 05 1992 15:27 | 12 | 
|  |     This won't work with new versions of ALL-IN-1 (certainly v3.0 - I think
    we may have made this change in v2.4 as well).
    
    WHY? you ask? Well, it's because although some escape sequences, like
    [5m, are fairly benign, others aren't. Some sequences can lock up your
    terminal, set it into funny modes, or worse. If you try typing a .EXE
    file (from DCL), you'll get some idea of the sort of things I mean.
    
    So, the LIST code in ALL-IN-1 now checks for ESC characters (and CSI)
    and outputs an error character (reverse question-mark I think) instead.
    
    Dave.
 | 
| 161.5 | GET OA$DCL | UTRTSC::BOSMAN | We're just sugar mice in the rain | Thu Mar 05 1992 15:52 | 3 | 
|  |     But you still can GET OA$DCL = "TYPE ... ", I presume.
    
    Sjaak.
 | 
| 161.6 |  | IOSG::SHOVE | Dave Shove -- REO-D/3C | Thu Mar 05 1992 15:59 | 3 | 
|  |     Oh yes, no problem (as long as you have DCL access).
    
    D.
 | 
| 161.7 | Try  .DISPLAY filename | MARVA1::POWELL | just another ADVENTURE-IN-1 player | Thu Mar 05 1992 18:12 | 8 | 
|  |     The Script Script command   .DISPLAY filename
    should still allow a text file with Escape sequences to work.
    Or did this function change in v3.0 too?
    
    I hope someone has documented these "minor" tweaks to the code
    (like in the release notes or some such place).
    There just COULD BE some customized application code that breaks
    as a result of all of the "fixes" I keep hearing about...
 | 
| 161.8 | Yes, .DISPLAY etc probably still do it | IOSG::SHOVE | Dave Shove -- REO-D/3C | Fri Mar 06 1992 11:10 | 19 | 
|  |     No, .DISPLAY (and probably .BOX etc) should still pass escape
    sequences.
    
    There's no need to change these - the essential difference is that the
    programmer gets to decide what's displayed. With LIST, especially when
    it's LISTing a mail message, neither the programmer nor the current
    user decide what's displayed - this is determined by what the sender
    put in the message. So it was possible to send "letter bombs" which
    would hang the user's terminal (or worse). 
    
    Note that this fix also stops those nice Christmas Card messages with
    falling snow etc. Pity.
    
    It should have been documented under "bug fixes" in the relevant
    version's Differences document. I can't check that just now. Sorry.
    Note that this was reckoned to be a "security fix" and so may not have
    been fully described.
    
    Dave.
 | 
| 161.9 | thanx | TROOA::VIAU | Over the hill and far away... | Fri Mar 06 1992 16:44 | 4 | 
|  |     Thank you all for your help.		
    
    Gene
    
 |