Timeline for Terminal Program To Save VI State
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2015 at 19:13 | answer | added | fakeleft | timeline score: 0 | |
| S Jul 16, 2014 at 17:36 | history | edited | ᔕᖺᘎᕊ | CC BY-SA 3.0 |
Add Vi tag
|
| S Jul 16, 2014 at 17:36 | history | suggested | Anthony Geoghegan |
Add Vi tag
|
|
| Jul 16, 2014 at 17:10 | review | Suggested edits | |||
| S Jul 16, 2014 at 17:36 | |||||
| Jul 16, 2014 at 17:07 | answer | added | Anthony Geoghegan | timeline score: 0 | |
| Sep 30, 2013 at 14:43 | comment | added | mveroone | You could create a directory of symlinks to the files you want openned, and make a script on startup that opens them all. just an idea | |
| Sep 30, 2013 at 13:03 | answer | added | sharkguto | timeline score: 0 | |
| Sep 30, 2013 at 12:30 | review | First posts | |||
| Sep 30, 2013 at 13:24 | |||||
| Sep 30, 2013 at 12:23 | comment | added | halexh | @Kwaio I suppose its more for the scenario when my machine crashes. For instance, on Friday, all of my terminals just decided to crash, yet other programs remained open and unaffected. First time I have experienced that in 3 years of using this machine though. | |
| Sep 30, 2013 at 12:14 | comment | added | mveroone | This may be off-topic, but most of the time, those settings are uneeded because linux hosts hardly nerver need a reboot. | |
| Sep 30, 2013 at 12:10 | history | asked | halexh | CC BY-SA 3.0 |