FreeBSD 10.0-RC5/amd64 When I edit a file containing the 0xa9/copyright/circle-c character. the line that the character is on is rendered as ~. It is not editable. It can't even e deleted. While nvi will allow stepping to the next line and continuing to edit, searching past the line fails and writing out the file truncated the file at the line. Unless a backup exists, the remainder of the file is lost.Since that character is usually early in the file, most of the file is lost. I don't know if other characters also trigger the problem. Is this a known issue? iconv related? It is VERY annoying! Fortunately I did have a backup and I usually use emacs. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman at gmail.com
On Fri, Jan 17, 2014 at 1:04 AM, Kevin Oberman <rkoberman at gmail.com> wrote:> When I edit a file containing the 0xa9/copyright/circle-c character. the > line that the character is on is rendered as ~. It is not editable. It > can't even e deleted. While nvi will allow stepping to the next line and > continuing to edit, searching past the line fails and writing out the file > truncated the file at the line. Unless a backup exists, the remainder of > the file is lost.Since that character is usually early in the file, most of > the file is lost. I don't know if other characters also trigger the problem. > > Is this a known issue? iconv related? It is VERY annoying! Fortunately I > did have a backup and I usually use emacs.Yes, and I do want to change its behavior. A workaround is invoke nvi with env LC_CTYPE=C nvi ... With "C" locale, nvi runs in plain old 8-bit mode. -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/
On 17/01/2014 07:04, Kevin Oberman wrote:> FreeBSD 10.0-RC5/amd64 > > When I edit a file containing the 0xa9/copyright/circle-c character. the > line that the character is on is rendered as ~. It is not editable. It > can't even e deleted. While nvi will allow stepping to the next line and > continuing to edit, searching past the line fails and writing out the file > truncated the file at the line. Unless a backup exists, the remainder of > the file is lost.Since that character is usually early in the file, most of > the file is lost. I don't know if other characters also trigger the problem. > > Is this a known issue? iconv related? It is VERY annoying! Fortunately I > did have a backup and I usually use emacs.Hi, Unfortunately nvi is really not unicode capable AFAIK. You probably want to switch to vim or another editor. Regards.
On Fri, Jan 17, 2014 at 1:04 AM, Kevin Oberman <rkoberman at gmail.com> wrote:> When I edit a file containing the 0xa9/copyright/circle-c character.Invoke nvi with env LC_CTYPE=en_US.ISO8859-1 nvi ... or type the following commend in nvi: :se fe=iso8859-1 The file encoding does not matche your locale setting. -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/