bug#11691: 24.1; shell-command-on-region leaves region marked

bug#11691: 24.1; shell-command-on-region leaves region marked

[Leo]

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

1. save the attached bug.el and b.txt file
2. emacs -q -l bug.el
3. In a terminal open b.txt by running: emacsclient -n b.txt

You should the whole buffer marked as shown in this screenshot.


[-- Attachment #2: scor.png --]
[-- Type: image/png, Size: 12622 bytes --]

[-- Attachment #3: Type: text/plain, Size: 89 bytes --]


It is caused by push-mark and exchange-point-and-mark in
shell-command-on-region.

Leo


[-- Attachment #4: bug.el --]
[-- Type: application/emacs-lisp, Size: 138 bytes --]

[-- Attachment #5: b.txt --]
[-- Type: text/plain, Size: 8 bytes --]

abc
xyz

bug#11691: 24.1; shell-command-on-region leaves region marked

[Lars Ingebrigtsen]

Leo <sdl.web@gmail.com> writes:

> 1. save the attached bug.el and b.txt file
> 2. emacs -q -l bug.el
> 3. In a terminal open b.txt by running: emacsclient -n b.txt
>
> You should the whole buffer marked as shown in this screenshot.

I can confirm that that is the case.

> It is caused by push-mark and exchange-point-and-mark in
> shell-command-on-region.
>
> Leo
>
> (setq format-alist
>       '((rot13 "rot13" "abc" "tr a-mn-z n-za-m" "tr a-mn-z n-za-m" t nil)))
> (setq server-use-tcp t)
> (server-start)

But...  this happens because you set `format-alist' to this rather
curious value?  Without this `format-alist' setting, things work as
expected.

So I'm not sure whether this is a bug or an expected result.  Anybody?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#11691: 24.1; shell-command-on-region leaves region marked

[Lars Ingebrigtsen]

Leo <sdl.web@gmail.com> writes:

> 1. save the attached bug.el and b.txt file
> 2. emacs -q -l bug.el
> 3. In a terminal open b.txt by running: emacsclient -n b.txt
>
> You should the whole buffer marked as shown in this screenshot.
>
>
> It is caused by push-mark and exchange-point-and-mark in
> shell-command-on-region.

I totally misunderstood what "it" was here -- the subject says it.  And
emacsclient does not have to be involved to reproduce it: It works fine
by just visiting the file normally.

I've now fixed this issue in Emacs 28.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no