The Kabal | 6 Jul 20:22 2014
Picon

Color highlighting feature request

Hello,

I noticed that for color highlighting, "Legal colors for foreground
and background color are: white, black, red, blue, green, yellow,
magenta, and cyan.".

I was attempting to create a close match to the "All Hallow's Eve"
color theme from Sublime Text 2, but noticed that I had very few
choices for colors in nano. By way of example, the 'comment' color
default for a PHP file in All Hallows Eve looks "purple". The closest
equivalent is the jarring magenta, which is really more of a bright
pink than a purple.

For environments with 256 color support, any chance we could get an
expanded selection of colors for syntax highlighting?

As always, your editor is awesome, many thanks for years of reliable
and easy to use editing.

- Patrick
Vampyrah Broadcasting | 13 Jun 21:29 2014
Picon

How to make all text bright?

Dear people,

How can I make all text bright?

Dennis
_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
Frank Schwenk | 12 Jun 09:18 2014
Picon

prevent nano from opening large files

Hi there,

i just made a huge mess as i had a large file open with "less" and by
pressing "v" accidentially i started the edit mode, which in this case
started nano.

Is it possible to prevent nano from opening large files? (.nanorc,
environment)

Regards

Frank
Mike Brown | 22 Mar 18:15 2014

command-line override of options set in .nanorc?

I usually want autoindent turned on, so my .nanorc has "set autoindent",
among many other customizations.

However, every once in a while, I need to copy-paste something that's 
preformatted, so it would be nice to be able to just override this one
setting when I invoke nano.

I was hoping there would be a command-line way to unset options that were set 
in the .nanorc. For example, for the single-letter options, you could use 
"-+" instead of "-", like in less(1):

  nano -+i

For the long option names, you would use an "unset" prefix:

  nano --unset-autoindent

There's no such capability, though, unless I'm missing something.
Is it possible? Maybe consider this a feature request.

(I realize I could remove the "set autoindent" from my .nanorc and instead
add -i or --autoindent to the command-line options, but it seems like the 
.nanorc is the ideal location for the things you want to be the defaults
most of the time, so I want to keep the autoindent set in there.)

Thanks for listening.
flyn jack | 12 Feb 05:32 2014
Picon

nanorc in Debian 7.3

OS Debian 7.3


I am confused. I know logic has its course, yet i need a definitive answer. The way that all instructions have a open end option to escape the legal weasel that is warm and fuzzy and could bite ones hand off, is frustrating at times.

Thank you.


man 1 nano or man 5 nanorc SYSCONFDIR/nanorc 


is described  


at a GNU page ' address below ' as “ files for configuring a host “ and “ This directory should normally be /usr/local/etc, but write it as $(prefix)/etc “.


So is it actually /etc  and not really  /usr/local/etc , while  /usr/local/ is empty in Debian 7.3


---------------------------

http://www.nano-editor.org/dist/v2.2/nano.1.html#INITIALIZATION FILE

INITIALIZATION FILE

nano will read initialization files in the following order: SYSCONFDIR/nanorc, then ~/.nanorc. Please see nanorc(5) and the example file nanorc.sample, both of which should be provided with nano.





--------------------------------------

http://www.gnu.org/prep/standards/html_node/Directory-Variables.html


‘sysconfdir’

The directory for installing read-only data files that pertain to a single machine–that is to say, files for configuring a host. Mailer and network configuration files, /etc/passwd, and so forth belong here. All the files in this directory should be ordinary ASCII text files. This directory should normally be /usr/local/etc, but write it as $(prefix)/etc. (If you are using Autoconf, write it as ‘ <at> sysconfdir <at> ’.)


_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
David T. Phillips | 31 Jan 02:32 2014

Default Behavior for Wrapping

(This is as much a comment as a question.)

By default, nano will wrap lines and this wrapping is done by inserting
line break characters into the file one is editing.

The behavior is overridable via -w/--nowrap.

For a computer programmer, sysadmin or just about anyone I can imagine
using a Unix text editor, the addition of characters to the file one is
editing can be a very bad thing.

As far as I can tell, nowhere in the man page does it mention that
wrapping involves inserting characters into your file.  I imagine many
people (I am one) equate wrapping with what is called 'soft wrapping' in
more recent versions of nano.

I'm just mentioning this because I feel like the default behavior should
be for the editor to do no (hard) wrapping.  If one wants wrapping they
should have to toggle it with --wrap or some such.

 <at> Chris - Thank you very much for all of your hard work.

-David

--

-- 
  David Phillips
  dave_phillips <at> elitemail.org
Komka Péter | 30 Jan 00:09 2014
Picon

Question: how to empty the cut-buffer

Hi,

How to clear the cutbuffer? (Without uncutting.)

Practically I am unable to do the most basic editing task, deleting some part of the text...
(No, the ^K and ^U is NOT a solution! If the text remains in the cutbuffer, then at the next text-relocating,
when I wanted to paste only the new stuff, the whole old stuff come back too!)

I am fully uncomprehending, how other folks can do this.

--

-- 
Komka Péter
Markus Bergholz | 18 Jan 19:12 2014
Picon

pipe to nano


Hi
any chance to pipe into nano without nano is immediately closing?


┌─[markus <at> x121e]─[/tmp]
└──╼ export LC_ALL=C
┌─[markus <at> x121e]─[/tmp]
└──╼ export EDITOR=nano
┌─[markus <at> x121e]─[/tmp]
└──╼ echo -e "test\ntemplate" | $EDITOR testfile.md
Received SIGHUP or SIGTERM

Buffer written to testfile.md.save
┌─[✗]─[markus <at> x121e]─[/tmp]
└──╼ cat testfile.md.save
test template



greetings
Markus
_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
Jimmy Chivers | 5 Dec 23:01 2013

Having a problem with nano

I have written some small c code files. I use gcc for the compiling. After it is compiled, the file worked as it should. Then when I reopened the file and it is not usable or readable. It says “converted from mac format”. Can you tell me what is wrong and how to fix? This happens on Raspberry Pi computer and on a PC with Ubunto. Thanks Jimmy Chivers

_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
Chris Allegretta | 24 Nov 19:38 2013

Re: nano differences from 2.0.6 to 2.2.6

Keeping on-list in case future folks run into the same issue.

Hmm, I installed the brew suite and ^space still works in 2.2.6.  Now
it's going to have to be something more subtle.  Can you let me know:

output of: brew info ncurses
Version of OS X you're using?
Any special keyboard type selected?

On 11/24/13, The Kabal <thekabal <at> gmail.com> wrote:
> Hello,
>
> No worries about the timing, glad to have you look into it.
>
> $TERM is xterm-256color. I'm using iTerm, but since you asked, I tested in
> regular Terminal.app as well, and get the same behavior I reported (2.0.6
> goes to the next word, 2.2.6 gives 'unknown command').
>
> Homebrew (http://brew.sh/) uses a recipe (
> https://github.com/Homebrew/homebrew-dupes/blob/master/nano.rb ) ,
> downloads 2.2.6, and then compiles it from source.
>
> This might help further, the brew info for the package:
>
> $ brew info nano
> nano: stable 2.2.6
> http://www.nano-editor.org/
> /usr/local/Cellar/nano/2.2.6 (42 files, 492K) *
> From: https://github.com/homebrew/homebrew-dupes/commits/master/nano.rb
> ==> Dependencies
> Required: homebrew/dupes/ncurses ✔
>
> I'm happy to send anything else that will help repro the bug.
>
> Thanks,
> Patrick
>
>
> On Sat, Nov 23, 2013 at 10:16 PM, Chris Allegretta <chrisa <at> asty.org> wrote:
>
>> ...or a week later.  Apologies for that.
>>
>> Hmm, having finally figured how to get gcc and the command line tools
>> on my mac again, compiling nano from source, I find that 2.2.6 does
>> just what I'd expect when I hit ^Space, no ket bindings needed...
>>
>> Couple questions here to see what's going on
>> Whats your $TERM set to?
>> Are you using the std mac Terminal program?
>> Is this homebrew version you're using just a binary, a source build
>> tool like Fink, the official nano source, or something else?
>>
>> On 11/16/13, Chris Allegretta <chrisa <at> asty.org> wrote:
>> > Hey Patrick, that sounds like a bug.  I'll take a look on my mac
>> > tonight or tomorrow.  Thanks for the report!
>> >
>> > On 11/15/13, The Kabal <thekabal <at> gmail.com> wrote:
>> >> Hello!
>> >>
>> >> In nano 2.0.6 (as shipped with OS X), Control-Space seems to default
>> >> to
>> >> "move cursor to next word". However, when I install the homebrew
>> >> version
>> >> of
>> >> 2.2.6, it appears to not be setup to do so.
>> >>
>> >> No worries, I thought, and pulled up the documentation, and found that
>> >> the
>> >> nanorc setting for that would seem to be "nextword". So I try a nanorc
>> >> with
>> >> a setting:
>> >>
>> >> bind ^Space nextword all
>> >>
>> >> But launching homebrew's nano 2.2.6 gives me 'Could not map name
>> >> "nextword"
>> >> to a function'.
>> >>
>> >> How do I get the same behavior in 2.2.6, that I had in 2.0.6, where
>> >> Control-space will move the cursor to the next word?
>> >>
>> >> Thanks for an awesome editor!
>> >> Patrick
>> >>
>> >
>>
>

_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano
The Kabal | 16 Nov 04:14 2013
Picon

nano differences from 2.0.6 to 2.2.6

Hello!

In nano 2.0.6 (as shipped with OS X), Control-Space seems to default to "move cursor to next word". However, when I install the homebrew version of 2.2.6, it appears to not be setup to do so.

No worries, I thought, and pulled up the documentation, and found that the nanorc setting for that would seem to be "nextword". So I try a nanorc with a setting:

bind ^Space nextword all

But launching homebrew's nano 2.2.6 gives me 'Could not map name "nextword" to a function'.

How do I get the same behavior in 2.2.6, that I had in 2.0.6, where Control-space will move the cursor to the next word?

Thanks for an awesome editor!
Patrick
_______________________________________________
Help-nano mailing list
Help-nano <at> gnu.org
https://lists.gnu.org/mailman/listinfo/help-nano

Gmane