bug#26107: Inaccurate location info for unbound-variable errors

2021-05-18 Thread Taylan Kammer
On 18.05.2021 22:11, Ludovic Courtès wrote: > Hi, > > Taylan Kammer skribis: > >> FWIW this seems fixed in 3.0, but I can reproduce with 2.2.7. >> >> Are we still supporting 2.2 for non-critical stuff? > > There’s no plan to do so. > > Ludo’. > Closing then. :-) -- Taylan

bug#26107: Inaccurate location info for unbound-variable errors

2021-05-18 Thread Ludovic Courtès
Hi, Taylan Kammer skribis: > FWIW this seems fixed in 3.0, but I can reproduce with 2.2.7. > > Are we still supporting 2.2 for non-critical stuff? There’s no plan to do so. Ludo’.

bug#26107: Inaccurate location info for unbound-variable errors

2021-05-18 Thread Taylan Kammer
FWIW this seems fixed in 3.0, but I can reproduce with 2.2.7. Are we still supporting 2.2 for non-critical stuff? -- Taylan

bug#26107: Inaccurate location info for unbound-variable errors

2017-03-15 Thread Ludovic Courtès
Hi! In 2.1.8/2.2.0, walking up the stack to find the origin of an unbound variable error yields inaccurate location info. Consider this: --8<---cut here---start->8--- (list 'a (symbol->string 'b) (symbol->string 'c) ;← unbound variable error repor