Am 13.03.2014 12:18, schrieb Andreas Röhler:
Hi Barry, hi all,
currently, when dedicated is on, a new buffer is created with some
autogenerated name.
Repeated dedicated calls will leave a row of badly readable buffer-names.
An alternative would be to kill the default shell before and run just a new
shell.
No idea WRT to pros and cons.
Also introducing a new switch here would be possible.
Any importance at all? Any suggestions?
Cheers,
Andreas
Quickly answering myself:
session mode - where state and output-buffer are kept/continued
dedicated - address/create an output buffer different from default
in combination:
not session, not dedicated - uses old/default cleaned-up output-buffer with new
process
session, not dedicated - re-uses old buffer, reads state (DEFAULT)
session, dedicated - continue last dedicated buffer
not session, dedicated - new process in new auto-generated output-buffer
_______________________________________________
Python-mode mailing list
Python-mode@python.org
https://mail.python.org/mailman/listinfo/python-mode
