Comment 1 for bug 1662341

Revision history for this message
Andreas Roehler (a-roehler) wrote :

Can't reproduce so far.

However, WRT unexpected region-shift where no mark was set,
the reason might be a previous yank, which does push-mark:

Lately someone wanted to shift a region also without transient-mark-mode
So I replaced (use-region-p) by

(and (mark) (not (eq (mark) (point))))

That might result in unexpected region-shifts maybe.

Solution would be to return to previous behavior as default, but have a boolean

py-shift-requires-transient-mark-mode-p

Have some idea what happened:

Lately enabled to shift a region also without transient-mark-mode
(use-region-p) was replaced by

(and (mark) (not (eq (mark) (point))))

That might result in unexpected region-shifts maybe.

Solution would be to return to previous behavior as default, but have a boolean

py-shift-requires-transient-mark-mode-p

default t, where nil would permit region without TMM