GNU bug report logs -
#31783
[PATCH v2] ido.el: define a special ido-fallback variable
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
> I believe this doesn't work, function parameters are always lexically
bound.
Indeed, there is even a warning from disassemble about the lexical argument
shadowing the dynamic one.
Thank you for noticing that.
> So I think your first patch was fine.
Fine.
To recap, the first patch also redefines "ido-fallback-command" so that it
accepts an optional parameter (the fallback command).
Is that ok for you? The idea was to let Ido be exited with a custom
fallback command through a function, and without requiring other packages
to set a variable directly.
Thank you.
On Mon, Jun 11, 2018 at 2:19 PM, Noam Postavsky <npostavs <at> gmail.com> wrote:
> merge 31783 31707
> quit
>
> Christophe Junke <junke.christophe <at> gmail.com> writes:
>
> > I agree that it is simpler to rename the existing variable, and just
> > add a defvar declaration. Here is a different version of the patch
> > which does only this.
>
> > +;; Indicates which fallback command to call when ido-exit is 'fallback.
> > +(defvar ido-fallback nil)
>
> > -(defun ido-buffer-internal (method &optional fallback prompt default
> initial switch-cmd)
> > +(defun ido-buffer-internal (method &optional ido-fallback prompt
> default initial switch-cmd)
>
> I believe this doesn't work, function parameters are always lexically
> bound. Compare
>
> ; -*- lexical-binding: t -*-
> (setq lexical-binding t) ; for use in *scratch*
>
> (defvar x nil)
>
> (disassemble (lambda (x y)
> (+ x y)))
>
> (let ((x 1))
> (disassemble (lambda (y)
> (+ x y))))
>
> So I think your first patch was fine.
>
[Message part 2 (text/html, inline)]
This bug report was last modified 6 years and 330 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.