Penguin

Differences between version 14 and previous revision of TabStops.

Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History

Newer page: version 14 Last edited on Sunday, July 23, 2006 9:13:41 pm by DanielLawson Revert
Older page: version 13 Last edited on Sunday, July 23, 2006 6:48:36 pm by AristotlePagaltzis Revert
@@ -60,5 +60,5 @@
 > !! The solution - tabstops that expand or shrink to fit their contents 
 
 > For as long as we continue to define each tabstop as being a multiple of N characters we will never be able to solve this problem satisfactorily. The problem is that we're using tabs and spaces to format text for aesthetic reasons rather than treating them semantically – tabs are for indenting and aligning text, spaces are for separating keywords. The solution then is to redefine how tabs are interpreted by the text editor. Rather than saying that a tab character (a "hard tab") will move the cursor until the cursor's position is a multiple of N characters, we should say that a tab character is a delimiter between table cells in a similar manner to how they're used in tab separated value (TSV) files. 
  
-Of course, the question is when (if ever) <tt>grep</tt>/<tt>patch</tt>/<tt>diff</tt>/<tt>sed</tt>/<tt>lpr</tt>/</ tt>less</tt> would be taught to follow this approach… 
+Of course, the question is when (if ever) <tt>grep</tt>/<tt>patch</tt>/<tt>diff</tt>/<tt>sed</tt>/<tt>lpr</tt>/<tt>less</tt> would be taught to follow this approach…