GNU bug report logs - #26305
25.0.90; backward-sexp doesn't jump over the whole assignment

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, lispercat <at> gmail.com
Cc: 26304 <at> debbugs.gnu.org, 26305 <at> debbugs.gnu.org
Subject: bug#26305: bug#26304: 25.0.90; last sexp is incorrect for ruby-mode
Date: Fri, 5 Feb 2021 15:23:37 +0200

On 05.02.2021 15:13, Lars Ingebrigtsen wrote:
> <lispercat <at> gmail.com> writes:
> 
>> When trying to evaluate following line:
>> arr = Array.new(100) { rand(1...100) }
>>
>> usng ruby-send-last-sexp (C-x C-e) gives an error.
>> Probably the whole line or just "Array.new(100) { rand(1...100) }"
>> should be considered as last sexp.
> 
> (I'm going through old bug reports that unfortunately got little response at
> the time.)

Thanks, I missed it. Will put it on my list.

> I can't find `ruby-send-last-sexp' in the Emacs source tree (or any sign
> that it's ever been there) -- is this from a third party package?

It's from inf-ruby. What is a sexp is determined by ruby-mode's SMIE 
grammar, though.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.