[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Nano-devel] behaviour with a BOM is different when poslog is set

From: Benno Schulenberg
Subject: [Nano-devel] behaviour with a BOM is different when poslog is set
Date: Fri, 27 Mar 2015 17:25:24 +0100

Hi all,

When in the nanorc file the option poslog is *not* set (or when
opening any file for the very first time), and the file contains
a BOM, the first <Right> wil appear to do nothing -- but what it
does is step away from the zero-width BOM.

When the option poslog is set, however, even when leaving the
cursor on the BOM before closing the file (by giving enough
<Left>s), upon reopening the file the cursor will be on the
character after the BOM -- a single <Right> will move the
cursor to the next character.

I think nano should behave the same in both cases and reput
the cursor on the BOM when it was left there.

This is of course a complete edge case -- who wants to have
BOMs in their files? -- but still, when wanting to be able to
give clear instructions on how to remove a possible BOM, it
would be nice if it didn't depend on what options were set
in nanorc...

Although... 'nano +1 filename' and hitting <Backspace> seems
to work fine every time.

So... consider the above mail as some kind of documentation.
Keywords: remove BOM, nano editor, Byte order mark, delete.


-- - Same, same, but different...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]