From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme: single quotes and hyphens
Date: Sat, 14 Dec 2013 19:22:42 +0100 [thread overview]
Message-ID: <CAOCRf5XTAMxEbzQ-9spAyKX7R2YHo3=Gtj4FiRD=5cidYCsqvA@mail.gmail.com> (raw)
In-Reply-To: <CAOCRf5U6NKAa7=LEjXrGVe+xuwrHY=ZBHz2tJ5=ZDXYNQk=9+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Also you can do
Edit , >od -x
To see a hexdump of a window.
2013/12/14 Bence Fábián <begnoc@gmail.com>
> It's your keyboard layout. acme does no such thing to my knowledge.
> Also it has nothing to do with the font. I assume you use p9p acme
> on Mac OS X based on your last letter. So I can't help you more.
>
>
> 2013/12/14 Blake McBride <blake@mcbride.name>
>
>> Greetings,
>>
>> While working with acme I had a problem with spell checking.
>> Investigating, I discovered that my setup of acme is not using normal
>> single quotes or hyphens. Instead of inserting what all other editors
>> insert when I hit my single quote or dash keys, acme is inserting some
>> other (2 byte?) character. I understand unicode but I am American-English.
>> My compiler and spell checker expect single byte, standard ASCII codes for
>> dash and single quotes. I absolutely can't use acme like this.
>>
>> I am using the standard font. Is there a way for me to correct this
>> behavior?
>>
>> Thanks.
>>
>> Blake McBride
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 1843 bytes --]
next prev parent reply other threads:[~2013-12-14 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 17:52 Blake McBride
2013-12-14 18:15 ` Bence Fábián
2013-12-14 18:22 ` Bence Fábián [this message]
2013-12-14 18:36 ` Blake McBride
2013-12-14 18:40 ` Bence Fábián
2013-12-14 19:22 ` Blake McBride
2013-12-14 19:30 ` Rubén Berenguel
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='CAOCRf5XTAMxEbzQ-9spAyKX7R2YHo3=Gtj4FiRD=5cidYCsqvA@mail.gmail.com' \
--to=begnoc@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).