Re: [PATCH 2/3] lisp/progmodes/etags.el don't (forward-char) as it's overriden next line

[Konstantin Kharlamov <hi-angel@yandex.ru>]

В Сб, мар 16, 2019 at 7:26 ПП (PM), Eli Zaretskii 
<eliz@gnu.org> написал:
>>  Date: Sat, 16 Mar 2019 18:42:44 +0300
>>  From: Konstantin Kharlamov <hi-angel@yandex.ru>
>>  Cc: emacs-devel@gnu.org
>> 
>>  >>  -    (and (eq selective-display t)
>>  >>  -	 (looking-at "\^m")
>>  >>  -	 (forward-char 1))
>>  >>       (beginning-of-line)))
>>  >
>>  > Did you actually try this change with selective-display in effect?
>>  > Because I'm not sure it is correct in that case.
>>  >
>>  > Thanks.
>> 
>>  Hmm… I will try a bit later, but the code seems really
>>  straightforward:
>>  	1. if current character is ^M, then step forward
>>  	2. step to the beginnig of the line
>> 
>>  The 2 undoes 1.
> 
> ^M has special meaning in selective-display mode.

Thanks, so, I just tried playing with the mode, and I haven't even 
found ^M anywhere. I wonder if the ^M being added by the mode is in the 
past, that just no longer happening.

Specifically, I did:

1. wrote in scratch buffer
test
 test
  test
2. evaluated (set-selective-display 1) which transformed the look of 
the text to
test...
3.α Tried searching for ^M by pressing C-s C-q C-m. It's failing to 
find anything.
3.β Put the caret before the triple dot, as in "test|...", and 
evaluated (char-after (point)) and (char-after (+ 1 (point))). The 
first returns "C-j" character, i.e. a newline; the second returns 
"space character". They're both the exact characters that actually are 
in text, as if I didn't enable selective-display.

So, even disregarding my patches (because I haven't managed to test 
this possible corner-case), the need for ^M workarounds is just no 
longer needed.