From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: reverse-menu-complete
Date: Sat, 27 Jun 2015 11:03:11 -0700 [thread overview]
Message-ID: <150627110311.ZM3603@torch.brasslantern.com> (raw)
In-Reply-To: <26732.1435387972@thecus.kiddle.eu>
(Please pardon lengthy context for very short comment below.)
On Jun 27, 8:52am, Oliver Kiddle wrote:
}
} - As a further complication, there is a "reverse_menu" hook which does
} the backwards movement. That becomes superfluous but I'm not sure how
} much of the hook would need to stay. Is the hook in theory an interface
} to third-party modules?
}
} diff --git a/Src/Zle/compresult.c b/Src/Zle/compresult.c
} index 9f383f4..7fec7c8 100644
} --- a/Src/Zle/compresult.c
} +++ b/Src/Zle/compresult.c
} @@ -1246,43 +1260,6 @@ do_menucmp(int lst)
} unmetafy_line();
} }
}
} -/**/
} -int
} -reverse_menu(UNUSED(Hookdef dummy), UNUSED(void *dummy2))
} -{
[...]
} diff --git a/Src/Zle/zle_tricky.c b/Src/Zle/zle_tricky.c
} index f18ad17..81a2395 100644
} --- a/Src/Zle/zle_tricky.c
} +++ b/Src/Zle/zle_tricky.c
} @@ -345,14 +345,8 @@ mod_export int
} reversemenucomplete(char **args)
} {
} wouldinstab = 0;
} + zmult = -zmult;
} + menucomplete(args);
}
} runhookdef(REVERSEMENUHOOK, NULL);
} return 0;
So what does the REVERSEMENUHOOK do, now that the reverse_menu function
is gone?
next prev parent reply other threads:[~2015-06-27 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 6:52 reverse-menu-complete Oliver Kiddle
2015-06-27 16:37 ` reverse-menu-complete Peter Stephenson
2015-06-27 18:03 ` Bart Schaefer [this message]
2015-06-27 21:34 ` reverse-menu-complete Oliver Kiddle
2015-06-27 23:35 ` reverse-menu-complete Bart Schaefer
2015-06-28 14:22 ` reverse-menu-complete Oliver Kiddle
2015-06-28 18:47 ` reverse-menu-complete Bart Schaefer
2016-02-26 20:55 ` reverse-menu-complete Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=150627110311.ZM3603@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).