From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 14 Dec 2013 12:36:14 -0600 Message-ID: From: Blake McBride To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=bcaec517201f7eb46f04ed82da55 Subject: Re: [9fans] Acme: single quotes and hyphens Topicbox-Message-UUID: 990d13d8-ead8-11e9-9d60-3106f5b1d025 --bcaec517201f7eb46f04ed82da55 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Apology. I started using a shell script I created to perform text wrap in acme by executing the script with |wrap Turns out it is my script (nroff version of groff) that is doing it. That should be easy to fix. Thanks, and sorry about the confusion. On Sat, Dec 14, 2013 at 12:15 PM, Bence F=E1bi=E1n wrote= : > 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 > >> 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-Engli= sh. >> 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 >> >> > --bcaec517201f7eb46f04ed82da55 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Apology. =A0I started using a shell script I created to pe= rform text wrap in acme by executing the script with |wrap
Turns out it= is my script (nroff version of groff)=A0that is = doing it. =A0That should be easy to fix.

Thanks, and sorry about the confusion.


On Sat, Dec 14, 20= 13 at 12:15 PM, Bence F=E1bi=E1n <begnoc@gmail.com> wrote:
It's your keyboard layo= ut. acme does no such thing to my knowledge.
Also it has nothing to do w= ith 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 ha= d a problem with spell checking. =A0Investigating, I discovered that my set= up of acme is not using normal single quotes or hyphens. =A0Instead of inse= rting what all other editors insert when I hit my single quote or dash keys= , acme is inserting some other (2 byte?) character. =A0I understand unicode= but I am American-English. =A0My compiler and spell checker expect single = byte, standard ASCII codes for dash and single quotes. =A0I absolutely can&= #39;t use acme like this.

I am using the standard font. =A0Is there a way for me = to correct this behavior?

Thanks.

Blake McBride



--bcaec517201f7eb46f04ed82da55--