Timeline for Issue with using ex commands
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 23, 2017 at 13:49 | history | bounty ended | Tyberius | ||
| S Jun 23, 2017 at 13:49 | history | notice removed | Tyberius | ||
| Jun 19, 2017 at 15:32 | comment | added | Tumbler41 | It doesn't produce the error after reattempting the code. | |
| Jun 18, 2017 at 8:45 | answer | added | B Layer | timeline score: 1 | |
| Jun 17, 2017 at 0:23 | comment | added | Tyberius | @Tumbler41 to clarify, it doesn't reproduce the error after reattempting or the code doesn't work as described? | |
| Jun 16, 2017 at 20:56 | comment | added | Tumbler41 | Could not reproduce on Windows7 Vim 8.0.586. I asked some people to try it on Linux, but they haven't got back. | |
| S Jun 16, 2017 at 17:21 | history | bounty started | Tyberius | ||
| S Jun 16, 2017 at 17:21 | history | notice added | Tyberius | Draw attention | |
| Jun 13, 2017 at 22:09 | comment | added | Tyberius | @Tumbler41 yeah it just opens the file in ex mode. | |
| Jun 13, 2017 at 22:02 | comment | added | Tumbler41 |
Ok, the ex confused me for a bit, but I'm assuming that ex is just aliased to vim on your system? (That's standard for Linux machines these days right?)
|
|
| Jun 13, 2017 at 21:41 | comment | added | Tyberius | @Tumbler41 I'm running these from the command line. The end goal was to incorporate them into a for loop. | |
| Jun 13, 2017 at 21:26 | comment | added | Tumbler41 |
When you give the code snippet, are you running that from a command line I.e. vim ex -c"... or are you running it from vim, :ex -c "... or is it in a vimrc ex -c"...?
|
|
| Jun 13, 2017 at 20:58 | review | First posts | |||
| Jun 14, 2017 at 6:00 | |||||
| Jun 13, 2017 at 20:56 | history | asked | Tyberius | CC BY-SA 3.0 |