git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3345 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3344 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

the hexadecimal character values are six digits long


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3343 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

regex can be included per line


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3342 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3341 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3340 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3339 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

options


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3338 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

string parameters don't need to be escaped with backslashes


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3337 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

again, as it's apparently valid


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3336 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3301 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

with backslashes in nanorc.5 and nanorc.sample


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3299 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3261 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

the "matchbrackets" rcfile option


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3259 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

the default regex string for quotestr, in order according to ASCII, and
add minor related documentation updates


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3256 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

option, to control whether nano adds magiclines to the ends of files


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3091 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

properly reject '"' and '''


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3058 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

handle '\"'


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3057 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3043 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

simplified by me


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3037 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3036 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

option, to control whether the word movement functions treat punctuation
characters as part of a word


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2983 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

a few tweaks


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2980 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2965 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

"default" syntax when necessary (the latter *is* actually ported mostly
from his patch with a few tweaks; the "default-syntax" option is
apparently something else entirely)


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2961 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

those files that don't match any other syntax's extensions (ported from
Brand Huntsman's old patch, but modified to work with a syntax named
"default" instead of requiring a "default-syntax" keyword, and to fit
into the existing color architecture)


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2959 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

tweaks


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2811 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

in the comment regex so that we don't match strings containing #'s
anymore


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2777 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

options in the documentation (e.g. "fill 0" acts just like "fill
[negative number]")


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2776 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

regexes like "color ,green" won't be colored as though they're invalid


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2775 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

syntax highlighting, via the "icolor" directive, and add it to those
regexes that can use it (ported from Brand Huntsman's old patch)


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2774 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2773 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2772 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2771 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2770 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

replace it with a literal space and a literal tab, so that include files
are properly colored again


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2766 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2764 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2763 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

apply to, and add "warning" and "error" to them as well


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2762 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

miscellaneous documentation fixes


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2714 35c25a1d-7b9e-4130-9fde-d3aeb78583b8