updates

AutoLangMode

@@ -1,11 +1,12 @@
 auto-lang.el is a minor mode that tries to find out the language of the current buffer/paragraph. It can set the ispell dictionary (see InteractiveSpell) accordingly and switch on flyspell (see FlySpell) for you.
 
-* http://www.marquardt-home.de/auto-lang.el
+* Original source: http://www.marquardt-home.de/auto-lang.el
+* A slightly updated version lives here: http://github.com/altruizine/auto-lang
 
-Supported languages are French, Spanish, Italian, Portugese, Danish, Swedish, Polish, Latvian, German and English, but it's easy to add support for a new language by introducing a new wordlist. 
+Supported languages are French, Spanish, Italian, Portugese, Danish, Swedish, Polish, Latvian, German and English, but it's easy to add support for a new language by introducing a new wordlist.
 If you have done so, please contribute it back.
 
-I don't consider this code finished nor nice, but it works for me. Tell me if you want to 
+I don't consider this code finished nor nice, but it works for me. Tell me if you want to
 help improve it.
 
 I should add support for iso-8859-15 to be used with a dictionary definition like this:
@@ -23,4 +24,4 @@ I should add support for iso-8859-15 to be used with a dictionary definition lik
 ----
 see also: AutoDictionaryMode
 ----
-CategorySpelling CategoryModes CategoryInternationalization GuessBufferLanguage GuessLang WikiSpell 
+CategorySpelling CategoryModes CategoryInternationalization GuessBufferLanguage GuessLang WikiSpell

AvallarkDotEmacsForWindows

@@ -1,3 +1,5 @@
+This is AbdulBijur's .emacs file
+
 You can download the latest emacs from : http://ourcomments.org/Emacs/EmacsW32.html
 
 Then follow the below steps :

CSharpMode

@@ -111,7 +111,7 @@ http://i42.tinypic.com/29pdmjd.jpg
 ||FlymakeCursor||||display flymake messages in the minibuffer, automatically, after a delay.||
 ||[http://code.google.com/p/csharpmode/source/browse/trunk/aspx-mode.el aspx-mode.el]||||multi-mode for editing ASPX files within emacs. Handles HTML, JS, CSS, and C#.||
 ||[[MSTFS]]||||Emacs integration with Team foundation server, via the tf.exe tool||
-||[http://stud4.tuwien.ac.at/~e0225855/linum/linum.html Linum.el]||||line numbers||
+||[http://stud4.tuwien.ac.at/~e0225855/linum/linum.html Linum.el]||||line numbers (See local elisp: Lisp:linum-ex.el)||
 ||[http://www.gnu.org/software/emacs/manual/html_node/emacs/Reverting.html Auto-Revert]||||refresh .cs buffers, after you've edited them externally, for example, in Visual Studio.||
 ||[http://code.google.com/p/csharpmode/source/browse/trunk/csharp-completion.el code completion] ||||Code completion elisp logic, that is integrated with csharp-mode.  It runs powershell as an inferior shell within emacs, to dynamically compile code snippets, and then introspect the result to provide realtime (subsecond) code completion in csharp buffers. To get it to work, you need the [http://code.google.com/p/csharpmode/source/browse/trunk/CscompUtilities.cs C# code], and be sure to read the [http://code.google.com/p/csharpmode/source/browse/trunk/Readme.txt readme]. Works only on Windows. Requires Powershell (free). Does not require Visual Studio, or SharpDevelop.||
 ||[http://ozymandias.dk/emacs/emacs.html#vj-complete vj-complete] ||||Is C# Code Completion in emacs really possible? This is an alternative code completion effort that pre-dates the above.||

EmacsApp

@@ -111,6 +111,10 @@ I have tried outlining 3 basic options for European users in a blog post/video [
 
 * Can not set default window position and size by  ./Emacs.app/Contents/MacOS/Emacs -q -g 400x400 or org.gnu.Emacs.plist. Is there another way to set default window size except from .emacs?
 
+[new:AlpAker:2011-05-23 19:29 UTC]
+
+Not without recompiling, unfortunately.  The NextStep (i.e., OS X) port explicitly disregards any geometry parameters that appear among the command line arguments (look at the the definition of `command-line-ns-option-alist' in lisp/startup.el).  It *should* read org.gnu.Emacs.plist, but the implementation of that is incomplete, so as you've found out, that method doesn't work either.  Your only options are to modify startup.el to pass size parameters to the initial make-frame command, or to change the values of ##DEFAULT_ROWS## and ##DEFAULT_COLS## in src/frame.c.  In either case, you'll have to rebuild the application.  -- AlpAker
+
 [new]
 * I'm missing an "emacs" binary, to execute from the command line, from Emacs.app. It's expected by some Makefiles, for instance. Does anyone know how to create or fake one? -- ThomasKappler
 

EmacsWikiSuggestions

@@ -470,6 +470,10 @@ I'd be interested in understanding how adding :: broke "in some way". I think it
 
 You are right in that the initial ##[ new::]## will get expanded before any text formatting rules are applied. These macros are applied before saving a page, not when rendering a page. That's why it has no access to HTML context, text formatting rules, and so on. I consider the feature (the expansion with timestamp and username) to be very minor and the effort to fix this appears to be a major undertaking. I'd rather remove the feature. Most of the uses I've seen only involve ##[new]## anyway, without the colons.
 
+[new:DrewAdams:2011-05-23 13:21 UTC]
+: I use ##[ new::]## and would like to continue to do so.  Having the timestamps is helpful to me. -- DrewAdams
+[new]
+
 As for wiki reorganization: I think it works just like a wish list for an open source project. If it doesn't scratch someone's itch, nobody is going to add it. I think it's a fundamental issue with our business model: there is no pay for boring stuff. Plus, 
 documentation is of no direct use for anything -- unlike code. Thus, people are mostly motivated to keep their own code and its documentation up to date. I don't think there is anything we can do about that. That's why the MissionStatement does not mention organization and quality.
 

Icicles_-_Apropos_Completions

@@ -25,7 +25,7 @@ Just as with prefix [[completion]], '''Icicles''' lets you cycle among the
 apropos candidates.  To do this, you use keys `next' and `prior' (labeled ##PageDown## and ##PageUp## on many keyboards). The root that was completed is
 ''underlined'' in the minibuffer completion candidate.
 
-For example, suppose you use `M-x' to enter a [[command]].  You don't
+For example, suppose you use `M-x' to enter a [[command]].  You do not
 remember the exact command name, but it has something to do with
 [[line]]s, so you type `M-x line', then hit `next' repeatedly until you
 see the right "<code>line</code>" command -- `transpose-lines', perhaps.  Prefix

Icicles_-_Candidate_Sets

@@ -137,7 +137,7 @@ some user interfaces by filling out a checklist followed by clicking `OK'.
 22) `mouse-1-click-follows-link' is an integer, then you will need
 to hold the mouse button depressed longer than that many seconds,
 or else that candidate will simply by chosen.  If the value is
-`t', then this won't work at all.  Any other value presents no
+`t', then this will not work at all.  Any other value presents no
 problem.  (Personally, I use `nil'.)]
 
 

Icicles_-_Candidates_with_Text_Properties

@@ -167,7 +167,7 @@ As a convenience, you can use function
 '''`icicle-candidate-short-help'''' to apply both
 `icicle-mode-line-help' and `help-echo' text properties to a candidate string.
 
-How does this work? '''Icicles''' redefines the standard Emacs function `display-completion-list' so that it retains text properties. Emacs should do the same, but it doesn't (yet).
+How does this work? '''Icicles''' redefines the standard Emacs function `display-completion-list' so that it retains text properties. Emacs should do the same, but it does not (yet).
 
 [new:DrewAdams:2007-01-24 15:19 UTC]
 : 2007-01-24 -- [[RMS]] has agreed to fix Emacs in this way, so this will become possible in Emacs. -- DrewAdams

Icicles_-_Completions_Display

@@ -179,7 +179,7 @@ matched portions of the candidates in `*Completions*'.  This
 portion is replaced by ellipsis, '''`##...##''''.  (In Emacs 20, it is
 replaced by nothing.)
 
-This can be useful when you don't care about the text that matches or when that text is particularly long.  For example, if
+This can be useful when you do not care about the text that matches or when that text is particularly long.  For example, if
 you use `icicle-find-file-absolute' (`C-u C-x C-f') and the
 completion candidates are absolute file names that share a
 common directory, it can be convenient to hide the directory

Icicles_-_Customization_and_General_Tips

@@ -1728,7 +1728,7 @@ minibuffer or called with a negative prefix argument.
 
 Non-`nil' user option '''`icicle-use-candidates-only-once-flag'''' means
 that acting on a candidate removes it from the set of available
-candidates, so that you don't see that it can be used again.
+candidates, so that you do not see that it can be used again.
 (`TAB' or `S-TAB' makes it available again.)  The default value
 is `nil', and you probably do not want to customize this.
 However, if you write EmacsLisp code that uses completion, then

Icicles_-_Cycling_Completions

@@ -61,7 +61,7 @@ Do not become a cycling drone! '''''Input some text to narrow the set of candida
 the set of candidates is small to begin with, then just cycling might be quick enough -- that is the case if you move among a small set of [[buffer]]s, for instance. But with '''Icicles''' you can profitably use cycling on even a very large set of candidates -- by filtering the set first. The reason this is often not very practical with vanilla Emacs is that filtering by a ''prefix'' only is not that potent -- '''Icicles''' regexp filtering changes this game.
 
 [:C-l]
-'''''Tip:''''' Whenever you type or delete text in the minibuffer, your partial input is remembered. When you cycle completion candidates, your input is replaced by each candidate, but you can at any time ''refresh the minibuffer'' to retrieve what you last typed. You do this with '''`C-l'''', which is bound in the minibuffer to command `icicle-retrieve-previous-input'. Editing a completion candidate that you have cycled into the minibuffer counts as input. Editing tells '''Icicles''' to remember what is in the minibuffer as your last real input. If you want to replace the candidate and go back to editing the input you had already typed before cycling, then use `C-l' -- don't just delete characters from the candidate.  See [[Icicles - History Enhancements]].
+'''''Tip:''''' Whenever you type or delete text in the minibuffer, your partial input is remembered. When you cycle completion candidates, your input is replaced by each candidate, but you can at any time ''refresh the minibuffer'' to retrieve what you last typed. You do this with '''`C-l'''', which is bound in the minibuffer to command `icicle-retrieve-previous-input'. Editing a completion candidate that you have cycled into the minibuffer counts as input. Editing tells '''Icicles''' to remember what is in the minibuffer as your last real input. If you want to replace the candidate and go back to editing the input you had already typed before cycling, then use `C-l' -- do not just delete characters from the candidate.  See [[Icicles - History Enhancements]].
 
 You can change the [[key]]s that are bound to completion-candidate cycling.  And you can change whether `down' and `up' start off by cycling prefix completions or apropos completions.  See [[Icicles - Customizing Key Bindings]].
 

Icicles_-_Defining_Icicles_Commands

@@ -14,9 +14,9 @@ Defining a [[command]] that uses '''Icicles''' [[completion]] and [[Icicles - Cy
 simple: just call `completing-read' or `read-file-name' to read
 input, then act on that input.  
 
-Nothing could be simpler -- just use `completing-read' or `read-file-name'! '''Icicles''' does the rest. This is the most important thing to learn about defining '''Icicles''' commands: ''you don't need to do anything'' except call `completing-read' or `read-file-name' as you would normally anyway. 
+Nothing could be simpler -- just use `completing-read' or `read-file-name'! '''Icicles''' does the rest. This is the most important thing to learn about defining '''Icicles''' commands: ''you do not need to do anything'' except call `completing-read' or `read-file-name' as you would normally anyway. 
 
-Or at least as I ''hope'' you would normally. I fear that many Emacs-Lisp programmers don't take sufficient advantage of `completing-read' when they could, using instead a function such as ''(quel horreur !)'' `read-string' to read user input.
+Or at least as I ''hope'' you would normally. I fear that many Emacs-Lisp programmers do not take sufficient advantage of `completing-read' when they could, using instead a function such as ''(quel horreur !)'' `read-string' to read user input.
 
 
 === Multi-Commands Are Easy To Define Too ===
@@ -43,7 +43,7 @@ identical to the definition of `icicle-buffer', except that the
 action function is `insert-buffer' instead of `switch-to-buffer'.
 
 The point is to not be afraid of defining multi-commands yourself.  You
-don't really need to have me add a multi-command to '''Icicles''' in
+do not really need to have me add a multi-command to '''Icicles''' in
 most cases; you can easily define it yourself.  Here is a simple
 definition of `icicle-insert-buffer'.  You will understand it in
 detail after reading the next section.
@@ -348,7 +348,7 @@ for some reason '''Icicles''' cannot be found or successfully loaded.
 
 But that brings up another question: What happens to your
 multi-command if '''Icicles''' is not available for a user, or s?he
-doesn't want to load it? No problem -- your multi-command then
+does not want to load it? No problem -- your multi-command then
 automatically turns into a normal, single-choice command --
 graceful degradation.
 

Icicles_-_Defining_Multi_M-x

@@ -51,10 +51,10 @@ There are a few things wrong with this definition, however. In the action functi
  (lambda (x) 
    (condition-case nil
        (funcall cmd x)                            ; Try to use a string candidate
-     (wrong-type-argument                         ; If that didn't work, use a
+     (wrong-type-argument                         ; If that did not work, use a
       (funcall cmd (car (read-from-string x)))))) ; symbol or number candidate.
 
-A similar problem occurs if the action function called doesn't accept a (single) argument. The best thing to do in this case is punt -- call `icicle-help-on-candidate' to display help on the candidate. To the code above, we add another error handler:
+A similar problem occurs if the action function called does not accept a (single) argument. The best thing to do in this case is punt -- call `icicle-help-on-candidate' to display help on the candidate. To the code above, we add another error handler:
 
  (wrong-number-of-arguments (funcall #'icicle-help-on-candidate))
 

Icicles_-_Emacs_Tags_Enhancements

@@ -84,7 +84,7 @@ A [[prefix argument]] changes the default behavior, as follows:
 [:icicle-find-first-tag-other-window]
 === `icicle-find-first-tag': Find First Tag in the Current Tags Table ===
 
-Sometimes you don't need the full power and flexibility of
+Sometimes you do not need the full power and flexibility of
 `icicle-find-tag'.  If you just want to find the first tag among
 several duplicates that match your input, and you just want to use
 the current tags table, then you can use '''`icicle-find-first-tag'''' or

Icicles_-_Global_Filters

@@ -28,10 +28,10 @@ not just programmers, some way to globally filter candidates.
 For example, if you have a command, such as `icicle-buffer', that
 reads a [[buffer]] name and displays the buffer, some users might
 always be interested only in buffers that are associated with
-files.  They don't want to see possible candidates like
+files.  They do not want to see possible candidates such as
 `*scratch*' and `*Messages*'.  What they need is a way to apply a
 global predicate that limits candidates to file-buffer names -- but
-they don't have access to the call to `completing-read' that is
+they do not have access to the call to `completing-read' that is
 inside the command definition.
 
 For this reason, some global filtering [[variable]]s are provided by '''Icicles''':

Icicles_-_Icompletion

@@ -64,7 +64,7 @@ delete. This '''[::incremental completion]''' is another form of icompletion, un
 The particular non-`nil' value of `icicle-incremental-completion-flag' determines when `*Completions*' is
 displayed and updated.  The default value, `t', means that
 `*Completions*' is updated only if it is already displayed.  Use `t'
-if you don't want `*Completions*' to be too intrusive but you want
+if you do not want `*Completions*' to be too intrusive but you want
 it to provide the most help when you ask for help (via `TAB' or
 `S-TAB').
 

Icicles_-_Info_Enhancements

@@ -25,7 +25,7 @@ choose node `##Isearch Yank##', whose name contains `yan' but does not
 start with it.  This is an obvious and standard '''Icicles''' feature.
 
 Although vanilla Emacs also accepts a substring as input for `i',
-it does not provide substring or regexp completion, and it won't
+it does not provide substring or regexp completion, and it will not
 accept a [[regexp]] as final input.
 
 '''Icicles''' binds `g', `i', and `m' to ''[[multi-command]]s''
@@ -148,7 +148,7 @@ virtual books, to use at any time.
 22) `mouse-1-click-follows-link' is an integer, then you will need
 to hold the mouse button depressed longer than that many seconds,
 or else that candidate will simply by chosen.  If the value is
-`t', then this won't work at all.  Any other value presents no
+`t', then this will not work at all.  Any other value presents no
 problem.  (Personally, I use `nil'.)]
 
 
@@ -222,7 +222,7 @@ with Emacs 22), and it is often less convenient than using
 `Info-search' (bound to `s' in Info).  '''Icicles''' searching is
 different from both, and it has its advantages and disadvantages.
 When you want the advantages of '''Icicles''' searching in Info, the
-flattening hack can be useful.  When you don't need those
+flattening hack can be useful.  When you do not need those
 advantages, other search methods can sometimes be more
 appropriate.