<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Correction: Much as I appreciate Paulo's contribution, I have to mention that the actual New Yorker article in which John McPhee describes his use of kedit is:</p>
<p style="margin-top:0;margin-bottom:0"><a href="https://www.newyorker.com/magazine/2013/01/14/structure" class="OWAAutoLink" id="LPlnk51169" previewremoved="true">https://www.newyorker.com/magazine/2013/01/14/structure</a>.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Michael<br>
</p>
<div id="LPBorder_GT_15658776395550.8222209184120763" style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id="LPContainer_15658776395430.05877237387424261" style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" role="presentation" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td id="ImageCell_15658776395470.1744881244376948" style="width: 250px; position: relative; display: table-cell; padding-right: 20px;" colspan="1">
<div id="LPImageContainer_15658776395480.38442018254794297" style="background-color: rgb(255, 255, 255); height: 140px; position: relative; margin: auto; display: table; width: 250px;">
<a id="LPImageAnchor_15658776395490.7381736174402844" style="display: table-cell; text-align: center;" href="https://www.newyorker.com/magazine/2013/01/14/structure" target="_blank"><img style="display: inline-block; max-width: 250px; max-height: 250px; height: 140px; width: 250px; border-width: 0px; vertical-align: bottom;" id="LPThumbnailImageID_15658776395490.6399958580318609" width="250" height="140" src="https://media.newyorker.com/photos/5909660bc14b3c606c10683a/16:9/w_1200,h_630,c_limit/130114_r23029_p886.jpg"></a></div>
</td>
<td id="TextCell_15658776395500.4991941712622039" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" colspan="2">
<div id="LPRemovePreviewContainer_15658776395500.47197153631594446"></div>
<div id="LPTitle_15658776395510.8235298762568137" style="top: 0px; color: rgb(26, 25, 25); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light", "Segoe UI Light", "Segoe WP Light", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; line-height: 21px;">
<a id="LPUrlAnchor_15658776395530.5475072763363938" style="text-decoration: none;" href="https://www.newyorker.com/magazine/2013/01/14/structure" target="_blank">Structure | The New Yorker</a></div>
<div id="LPMetadata_15658776395530.4031854809843963" style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; font-size: 14px; line-height: 14px;">
www.newyorker.com</div>
<div id="LPDescription_15658776395540.18608497509000832" style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;">
The approach to structure in factual writing is like returning from a grocery store with materials you intend to cook for dinner. You set them out on the kitchen counter, and what’s there is ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p></p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> texhax <texhax-bounces+michael.barr=mcgill.ca@tug.org> on behalf of texhax-request@tug.org <texhax-request@tug.org><br>
<b>Sent:</b> Thursday, August 15, 2019 6:00:03 AM<br>
<b>To:</b> texhax@tug.org <texhax@tug.org><br>
<b>Subject:</b> texhax Digest, Vol 2019, Issue 133</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send texhax mailing list submissions to<br>
texhax@tug.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://tug.org/mailman/listinfo/texhax">https://tug.org/mailman/listinfo/texhax</a><br>
or, via email, send a message with subject or body 'help' to<br>
texhax-request@tug.org<br>
<br>
You can reach the person managing the list at<br>
texhax-owner@tug.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of texhax digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Can anyone recommend a spell checker for tex files?<br>
(Paulo Ney de Souza)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 14 Aug 2019 20:17:37 -0700<br>
From: Paulo Ney de Souza <pauloney@gmail.com><br>
To: "Michael Barr, Prof." <barr.michael@mcgill.ca><br>
Cc: James Diamond <jim.diamond@acadiau.ca>, TeXhax <texhax@tug.org><br>
Subject: Re: Can anyone recommend a spell checker for tex files?<br>
Message-ID:<br>
<CAFVhNZNEqYgti_bME+tdpFiQHXAmyHsBy3Zc_ns=2jARrC6BKA@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ahhh ... KEdit, the DOS clone of the venerated XEdit that worked on VM/CMS.<br>
There are many people that swears by it and many that swear at it ... maybe<br>
someone should write a review-comparison of it and Emacs!<br>
<br>
The article by John McPhee is "Draft No. 4":<br>
<br>
<a href="https://www.newyorker.com/magazine/2013/04/29/draft-no-4">https://www.newyorker.com/magazine/2013/04/29/draft-no-4</a><br>
<br>
a very interesting piece of reading ...and so it is this article on him at<br>
NYT:<br>
<br>
<a href="https://www.nytimes.com/2017/09/28/magazine/the-mind-of-john-mcphee.html">
https://www.nytimes.com/2017/09/28/magazine/the-mind-of-john-mcphee.html</a><br>
<br>
I heard you can still buy KEdit:<br>
<br>
<a href="https://www.kedit.com/index.html">https://www.kedit.com/index.html</a><br>
<br>
but it is probably not worth it ...<br>
<br>
We are trying to make OpenDetex work in Windows:<br>
<br>
<a href="https://github.com/pkubowicz/opendetex">https://github.com/pkubowicz/opendetex</a><br>
<br>
so soon that coupled with Aspell (which runs fine on Windows) will give you<br>
an alternate path that will allow you to easily keep a private word-list.<br>
<br>
Paulo Ney<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Wed, Aug 14, 2019 at 1:50 PM Michael Barr, Prof. <barr.michael@mcgill.ca><br>
wrote:<br>
<br>
> Thanks all. It took longer than I wanted but the suggestion from Uwe<br>
> Ziegenhagen did the job. I finally downloaded the open office dictionary.<br>
> There doesn't seem to be a way to add additional words that I use all the<br>
> time, but it worked.<br>
><br>
><br>
> I actually have MS-Office on my computer (thanks to my computer centre<br>
> which makes Office 365 the only email interface) but simply could not find<br>
> their dictionaries.<br>
><br>
><br>
> As for what editor I use, I have been using it and its many upgrades for<br>
> 35 years and have tuned it highly to make it easy to do tex (e.g. the F-10<br>
> key lays down a pair of dollar signs and leaves the cursor between them;<br>
> F-11 and F-12 do the same for {} and () and there are other shortcuts) and<br>
> I am not about to change. What it doesn't have is an integrated<br>
> spell-checker. I used to have a very good one but it was a 16 bit program<br>
> that doesn't run under later Windows. The editor is called Kedit. John<br>
> McPhee once wrote a New Yorker essay about his use of it.<br>
><br>
><br>
> Anyway thanks for the help. It might amuse you to know that I went<br>
> through an entire 20+ page paper (at the insistence of a coauthor) and<br>
> didn't find a single actual misspelling.<br>
><br>
><br>
> Michael<br>
> ------------------------------<br>
> *From:* Paulo Ney de Souza <pauloney@gmail.com><br>
> *Sent:* Wednesday, August 14, 2019 4:30:25 PM<br>
> *To:* James Diamond <jim.diamond@acadiau.ca><br>
> *Cc:* Michael Barr, Prof. <barr.michael@mcgill.ca>; TeXhax <texhax@tug.org<br>
> ><br>
> *Subject:* Re: Can anyone recommend a spell checker for tex files?<br>
><br>
> The OP states that he uses a third-party editor. The tricky part here is<br>
> to get the TeX codes and commands cleared out of the file to be<br>
> spelled...not the speller itself since there are tons of them. This should<br>
> be the job of this third party editor or of TeXshop, luatex or even<br>
> detex...but my question is -- what is the application you used to run for<br>
> that? I am not aware of any under MS-Windows.<br>
><br>
> Paulo Ney<br>
><br>
> On Wed, Aug 14, 2019, 1:10 PM James Diamond via texhax <texhax@tug.org><br>
> wrote:<br>
><br>
> On Wed, Aug 14, 2019 at 17:11 (+0000), Michael Barr, Prof. wrote:<br>
><br>
> > All the answers I find on the web either require Luatex or that you be<br>
> running under some version of Unix. I use MS-windows and a third party<br>
> editor. I used to have a very good one, but it is 16 bit and all recent<br>
> versions of Win won't run it.<br>
><br>
> Michael,<br>
><br>
> I never use MS-windows, but aside from the texworks suggestion, you<br>
> could probably get a spell checker running under emacs, should that<br>
> appeal.<br>
><br>
> Jim<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://tug.org/pipermail/texhax/attachments/20190814/427cd66a/attachment-0001.html">https://tug.org/pipermail/texhax/attachments/20190814/427cd66a/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
texhax mailing list<br>
texhax@tug.org<br>
<a href="https://tug.org/mailman/listinfo/texhax">https://tug.org/mailman/listinfo/texhax</a><br>
<br>
------------------------------<br>
<br>
End of texhax Digest, Vol 2019, Issue 133<br>
*****************************************<br>
</div>
</span></font></div>
</body>
</html>