Martin Kealey

On Sat, 25 Feb 2017, Tom Hale wrote: > I've since learned that this particular `bash` idiom is not required as > with `set -e`, the exit status of the...

Or as noted in #839 just warn that trap 'err=$? ; my_exit_func ; exit $err' EXIT can be simplified to just trap my_exit_func EXIT since the `EXIT` trap saves `$?`.

@koalaman would having a specific warning that suggests changing ret=$? ; some_commands ; exit $ret to some_commands override and prevent _this_ warning? If not, would it be feasible simply to...

Aaargh, those references are depressing! (So much crummy code, so little lifetime left to complain about it.) Those latter two are "special": if the cleanup succeeds then explicitly exit using...

At least to have a beta-test program with uptodate versions.

It relation to item 2, perhaps adding a mode to have "visible format codes" while editing, so that it's immediately apparent when the format codes are being inserted wrongly. I...

1. Request: please document the available expansions. 1. Suggestion: create `${me}` as an expansion that's available in the channel & text lines; even without implementing the rest of this issue,...

@drmckay I like that idea too; like having a short-hand to a "reply" command that expands to `/msg ${channel} ${nick}: ${message}`. That said, I never find myself copying & pasting...

I would instead prefer that `/join `_`nick`_ opens a chat window with that user, without needing to specify any initial message. I know there's a technical difference in the background:...

Having `/msg #chan` open the window but not send an empty message would be acceptable. I think `/msg` would also be a good candidate for "switch to existing window" for...