Skip to content
Browse files

Cleanup leading whitespace

Set Vim modeline to harmonize with Emacs variables.
Change leading whitespace in file to follow those setting.
  • Loading branch information...
1 parent 7a03b06 commit a54fae1e6014778d7e58c86bb4ec3e80e38515d5 @RaimoNiskanen RaimoNiskanen committed Nov 5, 2012
Showing with 19 additions and 19 deletions.
  1. +19 −19 eeps/eep-0040.md
View
38 eeps/eep-0040.md
@@ -64,13 +64,13 @@ Reference
Names of sets of characters, XID\_Start, XID\_Continue, Lu, Lt, Lo, Pc,
Other\_Id\_Start, are drawn from [Unicode][] and [UAX#31][].
- Lu = upper case letters
- Lt = title case letters
+ Lu = upper case letters
+ Lt = title case letters
Ll = lower case letters
Lo = non-case letters (Arabic, Chinese, and so on)
Pc = connector punctuators, including the low line (_) and
a number of other characters like undertie (‿).
- Other_Id_Start = script capital p, estimated symbol,
+ Other_Id_Start = script capital p, estimated symbol,
katakana-hiragana voiced sound mark, and
katakana-hiragana semi-voiced sound mark.
@@ -108,19 +108,19 @@ Of course, someone might be using fonts
that do include say Arabic letters but not say the undertie. We can
deal with that by revising the underscore rule, which I recommend:
- Variable does not begin with a Pc character =>
- should not be a singleton.
+ Variable does not begin with a Pc character =>
+ should not be a singleton.
- Variable is just a Pc character and nothing else =>
- is a wild card.
+ Variable is just a Pc character and nothing else =>
+ is a wild card.
- Variable begins with a Pc character followed by an
+ Variable begins with a Pc character followed by an
Lu or Lt or Pc character =>
- may be a singleton.
+ may be a singleton.
- Variable begins with a Pc character followed by
- a legal character other than an Lu or Lt or Pc character =>
- should not be a singleton.
+ Variable begins with a Pc character followed by
+ a legal character other than an Lu or Lt or Pc character =>
+ should not be a singleton.
Thus ‿ is a wild-card, 隠者 is an atom, \_隠者 should not be
a singleton, but \_\_隠者 _may_ be a singleton. This rule is a
@@ -129,12 +129,12 @@ consistent generalisation of the existing rule.
Unquoted atoms
--------------
- unquoted_atom ::= "."? atom_start atom_continue*
+ unquoted_atom ::= "."? atom_start atom_continue*
- atom_start ::= XID_Start \ (Lu ∪ Lt ∪ "ªº")
+ atom_start ::= XID_Start \ (Lu ∪ Lt ∪ "ªº")
- atom_continue ::= XID_Continue ∪ "@" \ "ªº"
- | "." atom_start
+ atom_continue ::= XID_Continue ∪ "@" \ "ªº"
+ | "." atom_start
Again the choice of XID follows Python, and ensures that the
normalisation of an unquoted atom is still an unquoted atom.
@@ -222,13 +222,13 @@ why we have to ban "ª" and "º" for now. Later we may lift that ban.
There are three ways we have to customize the UAX 31 definition.
- - We have to continue to support "@" in variables and
+ - We have to continue to support "@" in variables and
"@" and "." in unquoted atoms for backwards compatibility.
- We have to continue to forbid unquoted atoms containing
the Latin-1 masculine and feminine ordinal indicators.
- - We have to distinguish between variables and unquoted atoms.
+ - We have to distinguish between variables and unquoted atoms.
There is a fourth way we _might_ customize it. Ken Whistler of
Unicode advises that he "doesn't see much point" in allowing Pc
@@ -315,4 +315,4 @@ This document has been placed in the public domain.
[EmacsVar]: <> "fill-column: 70"
[EmacsVar]: <> "coding: utf-8"
[EmacsVar]: <> "End:"
-[VimVar]: <> " vim: set fileencoding=utf-8 "
+[VimVar]: <> " vim: set fileencoding=utf-8 expandtab shiftwidth=4 softtabstop=4: "

0 comments on commit a54fae1

Please sign in to comment.
Something went wrong with that request. Please try again.