The def* commands (Was: [RP] Getting Through and Locking XTerm Width)

[Martin Samuelsson]

On Tue, Apr 12, 2005 at 01:48:59AM -0400, Shawn Betts wrote:
> There's *always* a way..you just have to lower your standards to allow
> more cheap hacks :).

I guess you're right. The last resort of binary patching the running
executable is always an existing option. (:

> I think the def* commands should stay around for compatibility with
> screen (though it grows less and less compatible). Is there a reason
> to remove them?

Ok, then I've misunderstood things.

The main reason for removing them would be that they clutter the
name space, but I guess I and others concerned by that can run unalias in
our own startup scripts¹...

Which brings us to the question, why does :unalias only accept one
argument? But that keeps the executable size down I guess, so maybe it's
the right behavior although other similar implementations accept to
unalias several aliases at a time.
--
/Martin

[1] This could be done in your zsh build script with something like:
    for alias in `grep add_alias\ \(\"def 
/usr/local/src/ratpoison/**/actions.c|sed 's/[^"]*"\([^"]*\)".*/\1/g'|sort|uniq`
        echo unalias $alias >> ~/dot/ratpoisonrc-unalias