[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to
From: |
Drew Adams |
Subject: |
bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one |
Date: |
Sun, 12 Oct 2014 16:01:58 -0700 (PDT) |
> the behavior is the same if no active region is
> available; if an active region IS available, the default is the
> contents of the region.
>
> Perhaps something like this should be added to (read-regexp),
> but that's a bigger proposal than this small patch.
I don't care what you do to hi-lock. However, wrt `read-regexp':
I certainly hope not. That would make that function useless for
any command that wants to act on the active region (e.g., vs
the buffer if inactive).
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Dima Kogan, 2014/10/12
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one,
Drew Adams <=
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Juri Linkov, 2014/10/14
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Drew Adams, 2014/10/14
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Juri Linkov, 2014/10/14
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Drew Adams, 2014/10/14
- bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Drew Adams, 2014/10/14
bug#18697: 25.0.50; [PATCH] hi-lock interactive functions now default to the active region, if there is one, Ivan Shmakov, 2014/10/13