>> I upgraded my system from opensuse 12.3 to 13.1 recently and accidetally
>> erased my nanorc C highlighting file. It its niether the first nor the last
>> file I will accidanally delete.
>> I said to myself, "Well the solution is trivial, just get the nano alpha
>> version from git." So I did but my syntax highlighting changes were not
>> there.
>> Why is it not there?
>
> Because the maintainer is very busy.
>
>> Please write me back and tell me what's up.
>
> You can still find your email with the attached highlighting changes here:
>
> http://lists.gnu.org/archive/html/nano-devel/2013-12/msg00000.html
>
> Again, the problem is not on your side. It's simply the case that none
> of the people who have commit access to the nano source repository
> have had the time to review your changes. This kind of thing stinks,
> and may be at some point they can bring in new people to help out with
> maintenance, but that's just how open source software works, when it's
> being maintained by people in their spare time.
>
> Cheers,
>
> Dirkjan
Whew, (wipes brow) Here I thought that there was something wrong with me/my code.
If I wanted to help the development of nano what do you recommend?
Yea, I know. The answers pretty big but I don't quite expect that everyone will
say as soon as I volunteer "Let's let him have rwx access to the whole repo! Yay!"
And if I decide to just help with anything else it may take time to look over my
changes. There is also the very real possibility that, should the people with write
access to the repo, if behind enough, will be unable to submit what I and others
have fixed fast enough and soon everyone will be fixing things on top of each other.
I have not yet tried to use ncurses but I have learned C programming
(though I'm probably not an expert yet.)
And I absolutely love extended regular expressions. I have such success with them!
And to think that people find them difficult! It is true though, that an increase
of power might be desirable. For instance, match anything without the word "include"
cannot be easily expressed as far as I know though perhaps like this
'[^(include)]' (Whether or not that is correct is unclear to me.)
Thanks, David