nano

nano with my custom patches
git clone git://bsandro.tech/nano
Log | Files | Refs | README | LICENSE

commit 14c62dbf11f539c1f98349bfb3f97622d7157ac7
parent f6fbc1572d51cfe9a8dbffc0c555a71f5217b46e
Author: Benno Schulenberg <bensberg@justemail.net>
Date:   Mon,  9 Jan 2017 14:28:33 +0100

build: check for GNU-style word-boundary support also in the tiny version

The tiny version can do regex searches nowadays, so the user might use
the \< and \> anchors in their regexes.

This fixes https://savannah.gnu.org/bugs/?50008.

Diffstat:
Mconfigure.ac | 11+++++------
1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/configure.ac b/configure.ac @@ -628,12 +628,10 @@ AC_CACHE_CHECK([for enhanced regular expression flag], nano_cv_flag_reg_extended AC_DEFINE_UNQUOTED(NANO_REG_EXTENDED, $nano_cv_flag_reg_extended, [Flag(s) to use to get the full range of extended regular expressions]) -if test x$color_support = xyes; then - # Now check for the end-of-word boundary support (/< and />). - AC_MSG_CHECKING([for GNU-style word boundary regex support]) - - AC_ARG_WITH(wordbounds, - AS_HELP_STRING([--with-wordbounds], [Use GNU-style word boundary delimiters]), +# Check for word-boundary support (/< and />). +AC_MSG_CHECKING([for GNU-style word boundary regex support]) +AC_ARG_WITH(wordbounds, +AS_HELP_STRING([--with-wordbounds], [Use GNU-style word boundary delimiters]), [ case "$with_wordbounds" in no) AC_MSG_RESULT(no) @@ -670,6 +668,7 @@ int main(void) ) ]) +if test x$color_support = xyes; then # if test x$CURSES_LIB_NAME = xcurses; then AC_MSG_CHECKING([whether _XOPEN_SOURCE_EXTENDED is needed]) AC_TRY_RUN([