View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000405 | MetaPost | feature request | public | 2010-05-26 07:33 | 2010-10-19 10:13 |
| Reporter | Taco | Assigned To | Taco | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.211 | ||||
| Target Version | 1.212 | Fixed in Version | 1.212 | ||
| Summary | 0000405: support openin_any / openout_any settings | ||||
| Description | Code is still missing | ||||
| Tags | No tags attached. | ||||
|
|
More notes from Karl (quoted text is me): > It still needs to run tex for label typesetting; that is the > only external command it runs (unless the user changes $MPXCOMMAND > explicitly, then all bets are off). More thoughts for the tracker item on putting mp into shell_escape_commands: - somehow have to arrange to ensure tex is invoked with paranoid settings -- we don't enable tex itself, at present. - probably need to arrange that MPXCOMMAND is not read from anywhere, but just uses a hardwired default. We can think more about this over the year. Heiko and/or Alexander Cherepanov sent several messages to tex-live regarding enabling tex back in fall 2009 when we were first thinking to enable restricted \write18. Thanks, k |
|
|
in revision 1421/1422 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-05-26 07:33 | Taco | New Issue | |
| 2010-05-26 07:33 | Taco | Status | new => assigned |
| 2010-05-26 07:33 | Taco | Assigned To | => Taco |
| 2010-05-28 08:52 | Taco | Note Added: 0000547 | |
| 2010-10-13 14:28 | Taco | Target Version | => 2.000 |
| 2010-10-17 12:27 | Taco | Target Version | 2.000 => 1.212 |
| 2010-10-19 09:32 | Taco | Note Added: 0000648 | |
| 2010-10-19 09:32 | Taco | Status | assigned => resolved |
| 2010-10-19 09:32 | Taco | Resolution | open => fixed |
| 2010-10-19 10:13 | Taco | Fixed in Version | => 1.212 |
| 2010-10-19 10:13 | Taco | Status | resolved => closed |
