some netbsd related changes

[yamt]

No description provided.

[lichray]

If we just want to eliminate the warnings, then we can do some compilation test in cmake.

[yamt]

If we just do not want to see the warnings, then we can do some compilation test in cmake.

i agree it would be better if it's possible.
i'm not going to do it by myself because i'm not familiar with cmake, though.

YAMAMOTO Takashi

[lichray]

The 'et' option does not replace the manually inserted tabs (like, just press TAB on the keyboard). Is that a desired behavior? AFAIK, vim replaces every tabs.

[yamt]

The 'et' option does not replace the manually inserted tabs (like, just press TAB on the keyboard). Is that a desired behavior? AFAIK, vim replaces every tabs.

it's exactly how NetBSD's nvi behaves.
because the author uses shiftwidth != tabstop.
http://mail-index.netbsd.org/tech-userlevel/2008/12/10/msg001482.html

yes, it's different from vim.

i have no strong opinion about what's a desired behaviour.

YAMAMOTO Takashi

[lichray]

On Sun, Mar 10, 2013 at 10:32 PM, YAMAMOTO Takashi <notifications@github.com

wrote:

it's exactly how NetBSD's nvi behaves.
because the author uses shiftwidth != tabstop.
http://mail-index.netbsd.org/tech-userlevel/2008/12/10/msg001482.html

Well, sounds reasonable. But... 'expandtab' does not seem to be
a good name for this. Maybe... expandshift -_-

Let me see if I can make it also expand tabs.

Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.

---

4BSD -- http://4bsd.biz/

[yamt]

i pushed another patch for this branch.
yamt@01eff8a
it isn't netbsd-specific but it was easier to do within the same branch for me because
it touches the same code as the following.
yamt@9ec5eba

[lichray]

On Mon, Mar 11, 2013 at 12:09 AM, YAMAMOTO Takashi <notifications@github.com

wrote:

i pushed another patch for this branch.
yamt@01eff8ahttps://github.com/yamt/nvi2/commit/01eff8a6ed6bea6f2f9b0ed07f3ff8a8eac356ba

I've heard of the problem; need some time to understand.

it isn't netbsd-specific but it was easier to do within the same branch
for me because
it touches the same code as the following.
yamt@9ec5ebahttps://github.com/yamt/nvi2/commit/9ec5eba57a0042b0432b928c918adde4128f36a9

Committed. Using a macro ICONV_TRADITIONAL given by CMake.

Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.

---

4BSD -- http://4bsd.biz/

[yamt]

i pushed another patch for this branch.
yamt@01eff8ahttps://github.com/yamt/nvi2/commit/01eff8a6ed6bea6f2f9b0ed07f3ff8a8eac356ba

I've heard of the problem; need some time to understand.

basically stateful encodings like iso-2022-jp need to go back to
the initial state before EOL. otherwise the next line would
start in a wrong state.

modifying the output state is done by outputing some additional bytes
(escape sequences) which don't have a corresponding input characters.

the function in question needs to tell iconv the end of input
by calling iconv(inbuf=NULL). so that iconv outputs the above
mentioned escape sequences.

YAMAMOTO Takashi

[lichray]

Merged in 2df7421 and 5740b1c. The expandtab option is adopted since f89afc9.