Timeline for Shell bash completion window
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2015 at 20:04 | history | edited | Matthew Piziak | CC BY-SA 3.0 | added kdb tags |
| Dec 23, 2014 at 10:51 | answer | added | Ehvince | timeline score: 3 | |
| Dec 23, 2014 at 2:41 | answer | added | Iqbal Ansari | timeline score: 5 | |
| Dec 22, 2014 at 21:35 | history | edited | Constantine | edited tags | |
| Dec 22, 2014 at 21:31 | comment | added | Matthew Piziak | As it turns out, I have ido-ubiquitous-mode already active. Deactivating it does not seem to affect the problematic behavior. | |
| Dec 22, 2014 at 21:27 | comment | added | Constantine | I would give ido-ubiquitous a try. (It is not shell-specific, but does promise to do what you need.) | |
| Dec 22, 2014 at 21:25 | comment | added | Matthew Piziak | @Constantine, you're absolutely right. I still get them confused sometimes. | |
| Dec 22, 2014 at 21:24 | history | edited | Matthew Piziak | CC BY-SA 3.0 | frame to window |
| Dec 22, 2014 at 21:18 | comment | added | Constantine | Do you really mean "Emacs creates a new frame"? (See Frames in the manual.) I think you mean "Emacs creates a new window. | |
| Dec 22, 2014 at 21:13 | history | asked | Matthew Piziak | CC BY-SA 3.0 |