Changes between Version 2 and Version 3 of Ticket #3770, comment 5


Ignore:
Timestamp:
03/10/17 11:33:16 (8 years ago)
Author:
rdmo
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3770, comment 5

    v2 v3  
    1 Testing some simpler conflicts between the `date` command and `mc`'s macro expansion...at the full-screen prompt – `bash` on my system AFAICT – available via Ctrl-O, expansion is done by `mc`then `date`: 
     1For example: the `date` command and `mc`'s macro expansion. Access is via the full-screen prompt –  `bash` on my system – toggled using `C-o`. There is no `mc` macro expansion. 
    22 
    33{{{ 
    … …  
    88}}} 
    99 
    10 ...and from the single-line prompt on the `mc` GUI, macro/variable expansion is done for `mc` first, then `date`: 
     10From the single-line prompt in `mc` , `mc` does macro expansion in order: `mc` first (1), then `date` (2). 
    1111 
    1212{{{ 
    13 # date +%d 
    14 # date +/the/current/working/directory 
     13# date +%d                             # (1) 
     14# date +/the/current/working/directory # (2) 
    1515/the/current/working/directory 
    1616 
    17 # date +%%d 
    18 # date +%d 
     17# date +%%d # (1) 
     18# date +%d  # (2) 
    191909 
    2020}}} 
    2121 
    22 Whether this is a bug or a feature can be argued both ways. The double percentage `%%` resolves some simpler issues where commands run as typed rather than as calls to run external programs. Perhaps the need for more comprehensive documentation is the issue this bug begins to highlight. More complex examples I cannot suggest at the moment. 
     22Use of the double percent symbols `%%` resolves simliar simpler issues. For complex examples perhaps this is not so. 
     23 
     24Note: edited for clarity.