background preloader

Text

Facebook Twitter

C#

Windows. Minimal. Vi. Kozaru. Gapbuffer. Wiki: EmacsFamily. Make Your Texts More Readable. Use proportionally spaced type. Monospaced type was created for typewriters to cope with mechanical limitations that do not affect type set by computers. With electronic type it is no longer necessary to accept the reduction in comprehension that goes with monospaced letters. When every character is the same width, the eye loses valuable cues that help it distinguish one letter from another. For this reason, no book or magazine is set in monospaced type. If you admire the typewriter look, choose a slab-serif face with proportional widths. Do not justify monospaced type. Internet Archive: Free Downloads: Text Archive. Notational Velocity. Readability - An Arc90 Lab Experiment.

Update: On February 1, 2011, Readability was re-launched into a full-fledged reading platform that includes mobile support, queuing articles for reading later and a greatly improved reading view. In addition, the platform provides a unique model for supporting publishers and writers through your reading activity. Visit to learn more. Reading anything on the Internet has become a full-on nightmare. As media outlets attempt to eke out as much advertising revenue as possible, we’re left trying to put blinders on to mask away all the insanity that surrounds the content we’re trying to read. It’s almost like listening to talk radio, except the commercials play during the program in the background. It’s a pretty awful experience. Our friend to date has been the trusty “Print View” button.

Recently, Mandy Brown wrote a wonderful article for A List Apart called In Defense Of Readers. Despite the ubiquity of reading on the web, readers remain a neglected audience. Maxime Crochemore. PyRoom Dev. Full screen Text Editor. TextRoom. Distraction free writing. Bean: An OS X Word Processor. Download Bean for High Sierra or Mojave Version 3.2.13 (released 3 May 2019) for macOS High Sierra (10.13) or macOS Mojave (10.14) • Not compatible with earlier macOS versions • Includes several bug fixes. Download Bean for Sierra Version 3.2.9 (released 14 November 2016) for macOS Sierra 10.12 • New in this version: even more bug fixes for Sierra • Spanish localization (Thank you, Francisco Ramón Román) Download Bean Version 3.2.5 (released 8 March 2013) OS X 10.5 to OS X 10.11 (El Capitan), Intel only Localized for: Brazilian Portuguese, Catalan, Chinese, Dutch, French, German, Italian, Polish, Slovak Changelog / News & Plans / Previous Versions Requirements / Installation Bean requires a Mac with an Intel processor, running at least OS X 10.5 Leopard or greater.

To install, double-click the downloaded file Bean-Install.zip. FAQ / Troubleshooting Answers to common questions about Bean are here. Cost / License / Sourcecode / Warranty Bean is provided at no monetary cost. Bean 3.x is closed source. 10 jQuery and non-jQuery javascript Rich Text Editors. Advertisement Introduction Javascript rich text editor has ease our life when we need to edit articles, post or even documents online. Most of the editors allow user to edit the content straight away (What You See Is What You Get - WYSIWYG), it just like editting a document with microsoft office. Nowadays, I think all of the content management system, blog systems are using rich text editor. LATEST VERSION: You can read our latest post about rich text editors: 10 Feature Packed Javascript WYSIWYG and Rich Text Editors So, here are the 10 RTEs that I can find online.

From the most basic support of font formatting to advanced features such as image upload, table creation, ajax support and so on. Advertisement MarkitUp - jQuery Official Website | Demo markItUp! Fast and unobtrusive integrationSupport for keyboard shortcutsAjax dynamic previewSupported: IE7, Safari 3.1, Firefox 2, Firefox 3. jWYSIWYG - jQuery Official Website | Demo Lightweight RTE- jQuery Official Website | Demo HTMLBox - jQuery. Text Editor Saving Routines. I have, for reasons that will become obvious in a week or so, been looking at text editors and what happens when you save a file.

For example, if we are editing the file filename.txt, different things will happen when you save the file depending on which editor you are using. VIM is fairly straight forward in that it renames the original file to filename.txt~, writes the modified contents to filename.txt, and then if that is successful deletes filename.txt~. Emacs does roughly the same thing as VIM, but by default doesn't clean up the filename.txt~ file. Eclipse is by far the simplest, truncating filename.txt to a length of 0 and then writing the new contents. Gedit is by far the most byzantine, first it writes the contents of the modified buffer to a hidden file .gedit-save-NNNN, then it renames the original file to filename.txt~, then renames .gedit-save-NNN to filename.txt and finally deletes filename.txt~.

Aoeui - Google Code. Markup's Where It's At. My first word processor ran in under 8K on a Commodore 64 and that included playing pomp and circumstance. It was adequate. It was markup based. When you wanted to view your work, you previewed the results. (When my friend John got a spell checker add-on, I was really impressed!) Next, I started using Apple Write (I think that was the name). All of those dot commands on the left margin. I got to the point where I didn’t need to preview, I knew what my stuff was going to look like. After that, I worked with Word Star on a CP/M emulator running on Apple IIE ’s.

But then there was WordPerfect. Here’s the thing, WordPerfect was logical. At the same time that Ultima IV came out, I decided to write a book for one of the classes I taught. I did this work (Ultima IV and WordPerfect) on my Leading Edge, 2 – 5.25” floppy drive system. WordPerfect never crashed (4.2 was solid, 4.0 no so much), and I knew what the resulting print was going to look like before it printed. These are low-level. Elastic tabstops - a better way to indent and align code. Intro - the status quo sucks Since the days of the character mapped display, programmers have argued over whether tabs or spaces should be used to line up text. While both strategies can be used if all of a project's programmers can agree on how many spaces wide a tab should be, experience has taught us that this is not always the case. Even if all of the programmers working on a project are diligent enough to stick to only using tabs or spaces and have tabs set to the agreed number of spaces, there is still a problem if any programmers wish to use modern proportional fonts (because a space is no longer the same width as every other character).

The reason why we have not yet settled conclusively on either tabs or spaces is that both camps can point to problems in the others' approach. The solution - move tabstops to fit the text between them and align them with matching tabstops on adjacent lines The simple solution is to redefine how tabs are interpreted by the text editor. Text Processing in Python. A couple of you make donations each month (out of about a thousand of you reading the text each week). Tragedy of the commons and all that... but if some more of you would donate a few bucks, that would be great support of the author.

In a community spirit (and with permission of my publisher), I am making my book available to the Python community. Minor corrections can be made to later printings, and at the least errata noted on this website. Email me at <mertz@gnosis.cx> . A few caveats: (1) This stuff is copyrighted by AW (except the code samples which are released to the public domain).

Feel free to use this material personally; but no permission is given for further distribution beyond your personal use. (2) The book is provided in "smart ASCII" format. Accidental Emacs. Nice to see Emacs getting a bit of press recently. I’ve used it for almost 20 years now and it dominates my time at the keyboard. It isn’t perfect and I’m reluctant to recommend it but I wouldn’t want to be without it. Let me explain. The best thing about Emacs is that it can do everything (including the things it can’t do yet). The worst thing about Emacs is finding out how it does anything. I wouldn’t call it discoverable. In fact, on several occasions, I’ve learned about Emacs by accident: you press the wrong key combination (easy to do when you’re holding down a couple of keys and stretching for a third) and, look, something interesting happens! The rest of this article describes a few of these happy accidents: modes I never knew about and tricks I wish I’d learned earlier.

Emacs the Operating System Whenever I see the Emacs splash screen (click on the graphic for a close-up) I’m amazed anyone ever gets past it. You can do basic editing with the menu bar and scroll bar using the mouse. Ten (mostly) false ideas about emacs. Text Algorithms in Ruby. Gap Buffer. Gap Buffer The gap buffer is a technique used by text editors that stores the entire text in a linear block of memory. It is a fairly simple technique that involves keeping track of 5 pointers and a sequencial block (gap) inside the buffer structure for inserting new text. The five pointers are (1) head of the buffer, (2) start of the gap, (3) first location outside the gap, (4) end of the buffer, and (5) location (point) within the buffer. The main rule for point is that it must be within the buffer and cannot be anywhere inside the gap other than the beginning of it. When text is to be written, the gap is moved to the point and new text can be written directly (each new character shrinks the gap by one).

More details on this technique can be found in Craig Finseth's "The Craft of Text Editing" which is now available online, and the usenet postings of Joseph Allen. What I've included is the source for a basic C++ implementation of gap buffer class which I hope will be useful to others. PyRoom: a writeroom clone in Python in Launchpad.