From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: UTF-8 character encoding
Date: Thu, 21 Jun 2018 18:49:00 -0000 [thread overview]
Message-ID: <83deb9a1a48a90dbbad9e0d1d50a139b@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <CAD8GWss253v-p+FjeonEqibr53v6wZRCQ+NWxBhb0LimQaM4sQ@mail.gmail.com>
On Wed, 20 Jun 2018 14:09:59, Lee wrote:
> I'm looking at
> https://cygwin.com/packaging-hint-files.html#pvr.hint
> and it starts off with
> Use UTF-8 character encoding.
>
> How do I do that and how do I check that I actually did use UTF-8
> character encoding _without_ using file?
[snip]
> I used vi to create both files & I'd like to understand why file says
> one is ascii & the other is utf-8
vim can tell you that in the statusline ...
:help statusline
:help encoding
Ask Google to help you with the details: GS: "vim show encoding in status".
E.g.
- http://vim.wikia.com/wiki/Show_fileencoding_and_bomb_in_the_status_line
(Show fileencoding and bomb in the status line)
As an example:
set laststatus=2
"set statusline=...
set statusline+=\ en:\ %{strlen(&enc)\ ?\ &enc\ :\ 'x'}
"set statusline+...
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-21 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 7:20 Lee
2018-06-21 10:12 ` Stefan Weil
2018-06-21 10:39 ` Andrey Repin
2018-06-22 7:31 ` Lee
2018-06-22 17:30 ` Andrey Repin
2018-06-25 9:56 ` L A Walsh
2018-06-25 20:52 ` Lee
2018-06-26 21:39 ` Thomas Wolff
2018-06-27 9:31 ` Lee
2018-06-27 7:50 ` Michael Enright
2018-06-27 9:34 ` Lee
2018-06-21 18:49 ` Houder [this message]
2018-06-21 20:46 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83deb9a1a48a90dbbad9e0d1d50a139b@smtp-cloud7.xs4all.net \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).