WikEmacs - User contributions [en]

Key Bindings

2012-04-30T13:46:18Z

Damd: Removing unnecessary anchor.

In Emacs, almost any keystroke, optionally combined with one or more modifier keys, or any sequence of such keystrokes, can be "bound" to any [[command]].

== Modifier keys naming convention ==

{| class="wikitable"
|-
! Modifier key
! Abbr.
! Remarks
! Example
! Action
|-
| Alt
| A
| Relatively seldom used in Emacs, because Meta is often "logically" mapped to the "physical" <tt>Alt</tt> key.
| A-x
| Type "x" while holding down the (non-Meta) Alt key
|-
| Control
| C
|
| C-x C-f
| While holding down Ctrl, type first "x" then "f". (This runs the command <tt>find-file</tt>).
|-
| Hyper
| h
| Often not mapped to any key (by default).
| h-x
| Type "x" while holding down hyper
|-
| Meta
| M
| Often mapped to <tt>Alt</tt> on your keyboard
| M-x find-file RET
| Either:
* type "x" while holding down Meta, or
* type "Esc" then "x"
(M-x activates the [[minibuffer]])

Then type "find-file" in the minibuffer, then Return.
|-
| Shift
| S
|
| S-x
| Type "x" while holding down Shift
|-
| Super
| s
| Often not mapped to any key by default, or to <tt>Window</tt> or <tt>Menu</tt> if present
| s-x
| Type "x" while holding down super
|-
|}

By convention, when multiple modifiers are specified, they go in alphabetical order: {{Keys|C-M-x}} not {{Keys|M-C-x}}.

== Printable cheat sheet for popular modes ==
Emacs ships with cheat sheets of common and useful key bindings.
The {{File|pdf}} files are located in the {{Directory|refcards}} subdirectory of {{Variable|data-directory}}.

== Change key bindings ==
You can add, remove and change key bindings for any command.

; {{Command|global-set-key}} or {{Command|local-set-key}}
: Hit the key sequence you want to bind
: Type the command to bind to that key sequence
: Invoke {{Keys|C-x ESC ESC|repeat-complex-command}}. The output you see is the full lisp command which does the binding. You can copy this to your {{EmacsConfigFile}}.

== External Links ==

* [http://www.masteringemacs.org/articles/2011/02/08/mastering-key-bindings-emacs/ Mastering Keybindings in Emacs]

[[Category:Customization]]
[[Category:Key Concepts]]

Java-mode

2012-04-30T13:44:49Z

Damd:

{{Infobox major-mode
|title = Emacs Lisp
|library = cc-mode
|command = java-mode
|builtin = yes
|auto activates = *.java
}}

'''java-mode''' comes with Emacs which provides very basic [[syntax highlighting]].

== Basic Setup ==

==See also ==
[[Java]]

[[Category:Java]]
[[Category:Programming languages]]

Keyboard macros

2012-04-30T13:40:53Z

Damd: /* Example usage */ Clarifying the scenario.

{{Manual|emacs|Basic-Keyboard-Macro|Basic Keyboard Macro}}

'''Keyboard macros''' can be used to automate or repeat tedious editing tasks in Emacs.

==Example usage==
Consider the standard <code>*scratch*</code> buffer:

<pre>
;; This buffer is for notes you don't want to save, and for Lisp evaluation.
;; If you want to create a file, visit that file with C-x C-f,
;; then enter the text in that file's own buffer.
</pre>

Suppose you want to remove the first occurrence of the letter "a" on every row in that piece of text. You could write a [[regular expression]] to do the job, but let's assume you want to use a keyboard macro this time.

# Make sure [[point]] is at the start of the buffer.
# Hit <code>C-x (</code> to start recording your macro. '''Note:''' If you hit <code>C-g</code> or if an error occurs, your keyboard macro recording will stop.
# Hit <code>C-s</code> followed by <code>a</code> to find the first "a". Now, point is right after the first "a" in the text.
# Hit backspace to delete that "a".

The first occurrence of "a" of the first line has been deleted. Let's move point to the beginning of the next line and then stop recording.

<ol start="5">
<li>Hit <code>C-e C-f</code> to move point to the beginning of the next line.</li>
<li>Hit <code>C-x )</code> to finish the recording of our macro.</li>
</ol>

The macro you have just recorded performs the operation of removing the first occurrence of "a" it can find and then moving point to the next line.

<ol start="7">
<li>Hit <code>C-x e</code> once to call that macro.</li>
<li>Continue hitting <code>e</code> to call it several times. Hit any other key to get out of the macro repetition.</li>
</ol>

==Repeating a macro==
To repeat a macro e.g. five times, you could hit <code>C-x e e e e e</code>. This could become tedious if you want to repeat it a greater amount of times, so an alternative is to provide a numeric argument to <code>C-x e</code>, e.g. <code>C-u 25 C-x e</code>.

===Repeating until there's an error===
Provide a <code>0</code> prefix argument to <code>C-x e</code> to execute a macro from point until there is an error, e.g. <code>C-u 0 C-x e</code> or <code>M-0 C-x e</code>. See [[prefix arguments]].

===Repeating a macro on every line in a region===
If you've recorded a macro which you want to call on every line in a buffer, you can use <code>C-x C-k r</code>, which applies the macro to every line in the region.

==Saving macros==
{{Manual|saving keyboard macros|(emacs) Save Keyboard Macro}}

===By name===
To give a macro a name which you can later call using <code>M-x</code>, hit <code>C-x C-k n</code>. Try to avoid strange characters in the name. Once you've given it a name, you can execute it using <code>M-x the-name-of-the-macro</code>.

===Binding to a key===
To bind a keyboard macro to a key using <code>C-x C-k b</code>. To avoid problems caused by overriding existing bindings, the key sequences <code>C-x C-k 0</code> through <code>C-x C-k 9</code> and <code>C-x C-k A</code> through <code>C-x C-k Z</code> are reserved for your own keyboard macro bindings. You can, however, bind a keyboard macro to whatever you like.

===Saving it permanently===
To save a keyboard macro for future Emacs sessions, go to your init file (or wherever you want to store it) and hit <code>M-x insert-kbd-macro</code>. Then enter the name of the macro you would like to save. This will insert Emacs Lisp code which defines the macro you chose, so you can use it in future sessions.

Using the example in the beginning of this article, let's say you named that macro <code>remove-first-a</code>. If you use <code>insert-kbd-macro</code> to insert the Lisp for that macro, this is what would come up:

<pre>
(fset 'remove-first-a
(lambda (&optional arg) "Keyboard macro." (interactive "p") (kmacro-exec-ring-item (quote ([19 97 13 backspace 5 6] 0 "%d")) arg)))
</pre>

If you have bound the macro to a key as described in the previous section, you can generate the code for that as well by prefixing the insert-kbd-macro call with [[prefix argument|<code>C-u</code>]].

[[Category:Intermediate]]
[[Category:Editing]]

Talk:ERC

2012-04-06T21:50:32Z

Damd:

==The "common" customizations==
Please, whoever put it there, remove it. Let's not have this wiki turn into the old EmacsWiki. [[User:Damd|damd]] 15:45, 5 April 2012 (EEST)
: apologies for the ignorance, but I don't understand what you mean. do you mean we should n't put any customisation information in a page.? How would a reader know how to use a package with out that information.? -- [[User:Kindahero|Kindahero]] 16:36, 5 April 2012 (EEST)
: I think that [[User:Damd|damd]] meant that customization should be finer grained - a separate section for "set nick", "set autojoin channels"", "autoreconnect". [[User:Bozhidar|Bozhidar]]
::I mean that we should try to not dump all of our customizations into the main article. People make all kinds of customizations to ERC, but what the article should describe is how to make it work out of the box. Instead of immediately describing how to write a command for connecting to one's favorite IRC networks, we should describe how ERC works out-of-the-box. This means instructions on how to customize the default ERC nickname, how to connect to a different server, how to switch between channels, how logging works, etc.
::The biggest problem with EmacsWiki, in my opinion, is that there is no clear distinction between discussions, "useful" customizations (i.e. someone's homebrew Emacs Lisp) and information about how to actually use whatever part of Emacs that's described. Simply dumping one's custom code into the article is a *huge* step in the wrong direction. [[User:Damd|damd]] 00:50, 7 April 2012 (EEST)

Main Page

2012-04-05T18:17:03Z

Damd: Replacing Emacs explanation image.

'''WikEmacs''' (pronounced wiki-macs) collects useful resources for working with [[GNU Emacs]]. Think of it as a
'''next generation, better structured and improved [http://www.emacswiki.org/ Emacs Wiki]''' .
[[File:Emacs-explanation.png|320px|thumb|right|Basic terminology of typical Emacs GUI Frame]]

---------
'''First time visitors''' can start [[#Explore WikEmacs | exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs. We want to keep you excited and engaged.

-----------
We need more '''[[:Category:WikEmacs Contributor|WikEmacs Contributor]]s'''. You can help the following way.

{{Note| First of all, Please take a minute to look at
[[WikEmacs:Guidelines]] before start editing.}}

* Priority tasks
** Migrate content from [http://www.emacswiki.org EmacsWiki]. Please adopt the following approach -''I found this on EmacsWiki which was helpful. But it took me a lot of time to find it. Now that I have found it, I will put it in WikEmacs so that others can benefit from it.''

* Intermediate tasks
** Provide tutorials or content for the [[:Category:Popular Package|Popular Packages]] or [[:Category:Native Package|Native Packages]].
** Add more content to [[Special:ShortPages]]
** Document or add more [[:Category:Third Party Package|Third Party Package]]s

* Other tasks
** Copy edit [[Special:RecentChanges]] or be a moral police
** Add more members to various [[Special:Categories]]
** Categorize one of these pages [[Special:UncategorizedPages]]

----
'''Emacs News'''

The latest stable release of Emacs is [[GNU Emacs 23|Emacs-23.4]].
The next major release is [[GNU Emacs 24|Emacs-24.1]] and is in ''Pretest'' stage.

Emacs is available on all popular [[:Category:Install Or Upgrade| Operating Systems]] including [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on BSD |BSD]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].

= Explore WikEmacs =

To explore WikEmacs proceed as follows:
* Search for or visit a page of interest
* At the end of the page, there is a list of categories
* Click on individual categories and it will give you a list of all pages that will be of interest to you.

== What is your comfort level with Emacs? ==
* [[:Category:Beginner|Beginner]]
* [[:Category:Intermediate|Intermediate]]
* [[:Category:Expert|Expert]]
** Are you a maintainer of a [[:Category:Built-in Package|Built-in Package]]? If you don't find information about your package, please add it. No one else is better than your are to write about it.
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.
* [[:Category:Vim User|Vim User]]
* [[:Category:User Level|Other]]

== What do you want to accomplish now? ==
* [[:Category:Install Or Upgrade|Install Or Upgrade]]
* [[:Category:Customization|Customize Emacs]]
* [[Key Bindings|Tweak Key Bindings]]
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]

== What do you use Emacs for? ==
* [[:Category:Text Editing|Text Editing]]
* [[:Category:Programming|Programming]]
* [[:Category:Document authoring|Document authoring]]
* [[:Category:Organizer|Getting Organized]]
* [[:Category:Email|Emailing]]
* [[:Category:Chat|Chatting]]
* [[:Category:Blogging|Blogging]]
* [[:Category:Browse|Browsing]]
* [[:Category:Workflow|Other]]

== How do you involve yourself with the community? ==
* [[:Category:Emacs User]]
* [[:Category:Emacs Contributor]]
* [[:Category:WikEmacs Contributor]]
* [[:Category:User Role|Other]]

[[Category:WikEmacs]]

File:Emacs-explanation.png

2012-04-05T18:16:31Z

Damd: Explanation of the different parts of an Emacs GUI.

Explanation of the different parts of an Emacs GUI.

Talk:ERC

2012-04-05T12:45:23Z

Damd: Created page with "==The "common" customizations== Please, whoever put it there, remove it. Let's not have this wiki turn into the old EmacsWiki. ~~~~"

==The "common" customizations==
Please, whoever put it there, remove it. Let's not have this wiki turn into the old EmacsWiki. [[User:Damd|damd]] 15:45, 5 April 2012 (EEST)

Talk:Main Page

2012-04-01T16:13:40Z

Damd: /* Syntax highlighting */

== IMPORTANT: Offline discussion ==

There is a Google group for discussion of the site: https://groups.google.com/forum/?fromgroups#!forum/wikemacs so we should probably favor posting there. [[User:PhilHudson|PhilHudson]] 16:16, 26 March 2012 (EEST)

== Structure ==
I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)

This seems like a good idea. Might help us utilize better the screen estate. As for the relation to the EmacsWiki - it is more or less non-existing. We have the permission from Alex (kensanata) to migrate any content we choose to, but they won't be supporting us in any way. [[User:Bozhidar|Bozhidar]] 20:28, 26 March 2012 (EEST)

== Markup Conventions==

=== Wikipedia linking convention ===

Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)

=== EmacsWiki linking convention ===

Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)

== Describing Modes and Packages ==

=== Naming Conventions ===

I'd like to suggest *not* suffixing (links to) modes with "-mode". Thus: "org" not "org-mode". For consistency I've been adding links titled "org-mode" until now, since that one was already created when I started. [[User:PhilHudson|PhilHudson]] 22:09, 24 March 2012 (EET)

:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]

:I actually disagree. E.g. [[Java]] could be a page describing the different Java capabilities of Emacs, with links to the different JavaScript modes. This is especially true for [[JavaScript]], where the [[js-mode]] shipped with the latest Emacs is completely different from the other widely used [[js2-mode]] by Yegge. [[User:Damd|Damd]] 18:20, 25 March 2012 (EEST)

::Hm, good point about disambiguation... I still like the idea of using "titles" vs "commands", though. E.g. a [[Java]] page describing the built-in support (Java Mode) and then linking to articles on related packages (JDEE, etc) and why you might consider them instead. [[User:GregLucas|GregLucas]] 19:32, 25 March 2012 (EEST)

:::How would we handle e.g. [[Haskell]]? Emacs doesn't ship with any Haskell mode as far as I know... [[User:Damd|damd]] 19:58, 25 March 2012 (EEST)

== Template for mode-with-github-source pages? ==

Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)

== Issues ==
* The "Editing Help" link goes to a virgin page, not the full help page.
* Add [http://meta.wikimedia.org/wiki/Help:Footnotes Mediawiki Cite extension] to enable footnotes.
* Add [http://meta.wikimedia.org/wiki/Category#Visualizing_category_tree Category Tree extension] to explore various categories like [[:Category:Programming languages]].

== Syntax highlighting ==

Could we install a MediaWiki plugin which lets us do proper syntax highlighting of different languages? [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi] looks like a good alternative. [[User:Damd|damd]] 20:07, 25 March 2012 (EEST)

:I've already installed it, but it doesn't seem to work properly (the fonts seem terribly small) and it doesn't support Emacs Lisp. [[User:Bozhidar|Bozhidar]] 20:24, 26 March 2012 (EEST)

::Are you sure the font size is not because of your web browser settings? They look just fine when I try it. About the Elisp support, we can still use just "lisp" until someone gets around to writing a version for Elisp. [[User:Damd|damd]] 18:44, 31 March 2012 (EEST)

::: I also found font size in the code snippets are inconveniently low. I dont have any special settings for my browser. I am on recent firefox. [[User:Kindahero|Kindahero]] 18:52, 31 March 2012 (EEST)

::::We could customize the CSS for the syntax highlighting plugin, but first let's make sure it's actually something in the CSS that causes this.
::::<pre>This is just an ordinary PRE element.</pre>
::::<syntaxhighlight lang="html4strict">This is a PRE element generated by the syntax highlighting plugin.</syntaxhighlight>
::::Is the font in both examples too tiny? If so, I suggest you check your browser settings. You can configure this in the "Content" section of Firefox's settings. [[User:Damd|damd]] 19:13, 1 April 2012 (EEST)

== fails to create thumbnails ==

I think some adminstative settings must be made in order to produce thumbnails of the pictures automatically. Can anyone do this .? check out [[Dictem]] to see what I am talking about. [[User:Kindahero|Kindahero]] 16:21, 31 March 2012 (EEST)
: found this link, http://www.mediawiki.org/wiki/Manual:Configuration_settings#Thumbnail_settings [[User:Kindahero|Kindahero]] 16:24, 31 March 2012 (EEST)
:: another link, http://www.mwusers.com/forums/showthread.php?1334-Resized-thumbnail-images-not-displaying Feel free to delete these links [[User:Kindahero|Kindahero]] 16:28, 31 March 2012 (EEST)

Talk:Main Page

2012-03-31T15:44:31Z

Damd: /* Syntax highlighting */

== IMPORTANT: Offline discussion ==

There is a Google group for discussion of the site: https://groups.google.com/forum/?fromgroups#!forum/wikemacs so we should probably favor posting there. [[User:PhilHudson|PhilHudson]] 16:16, 26 March 2012 (EEST)

== Structure ==
I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)

This seems like a good idea. Might help us utilize better the screen estate. As for the relation to the EmacsWiki - it is more or less non-existing. We have the permission from Alex (kensanata) to migrate any content we choose to, but they won't be supporting us in any way. [[User:Bozhidar|Bozhidar]] 20:28, 26 March 2012 (EEST)

== Markup Conventions==

=== Wikipedia linking convention ===

Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)

=== EmacsWiki linking convention ===

Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)

== Describing Modes and Packages ==

=== Naming Conventions ===

I'd like to suggest *not* suffixing (links to) modes with "-mode". Thus: "org" not "org-mode". For consistency I've been adding links titled "org-mode" until now, since that one was already created when I started. [[User:PhilHudson|PhilHudson]] 22:09, 24 March 2012 (EET)

:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]

:I actually disagree. E.g. [[Java]] could be a page describing the different Java capabilities of Emacs, with links to the different JavaScript modes. This is especially true for [[JavaScript]], where the [[js-mode]] shipped with the latest Emacs is completely different from the other widely used [[js2-mode]] by Yegge. [[User:Damd|Damd]] 18:20, 25 March 2012 (EEST)

::Hm, good point about disambiguation... I still like the idea of using "titles" vs "commands", though. E.g. a [[Java]] page describing the built-in support (Java Mode) and then linking to articles on related packages (JDEE, etc) and why you might consider them instead. [[User:GregLucas|GregLucas]] 19:32, 25 March 2012 (EEST)

:::How would we handle e.g. [[Haskell]]? Emacs doesn't ship with any Haskell mode as far as I know... [[User:Damd|damd]] 19:58, 25 March 2012 (EEST)

== Template for mode-with-github-source pages? ==

Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)

== Issues ==
* The "Editing Help" link goes to a virgin page, not the full help page.
* Add [http://meta.wikimedia.org/wiki/Help:Footnotes Mediawiki Cite extension] to enable footnotes.
* Add [http://meta.wikimedia.org/wiki/Category#Visualizing_category_tree Category Tree extension] to explore various categories like [[:Category:Programming languages]].

== Syntax highlighting ==

Could we install a MediaWiki plugin which lets us do proper syntax highlighting of different languages? [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi] looks like a good alternative. [[User:Damd|damd]] 20:07, 25 March 2012 (EEST)

:I've already installed it, but it doesn't seem to work properly (the fonts seem terribly small) and it doesn't support Emacs Lisp. [[User:Bozhidar|Bozhidar]] 20:24, 26 March 2012 (EEST)

::Are you sure the font size is not because of your web browser settings? They look just fine when I try it. About the Elisp support, we can still use just "lisp" until someone gets around to writing a version for Elisp. [[User:Damd|damd]] 18:44, 31 March 2012 (EEST)

== fails to create thumbnails ==

I think some adminstative settings must be made in order to produce thumbnails of the pictures automatically. Can anyone do this .? check out [[Dictem]] to see what I am talking about. [[User:Kindahero|Kindahero]] 16:21, 31 March 2012 (EEST)
: found this link, http://www.mediawiki.org/wiki/Manual:Configuration_settings#Thumbnail_settings [[User:Kindahero|Kindahero]] 16:24, 31 March 2012 (EEST)
:: another link, http://www.mwusers.com/forums/showthread.php?1334-Resized-thumbnail-images-not-displaying Feel free to delete these links [[User:Kindahero|Kindahero]] 16:28, 31 March 2012 (EEST)

Unit Testing

2012-03-26T07:30:04Z

Damd: moved Unit Testing to Unit testing

#REDIRECT [[Unit testing]]

Unit testing

2012-03-26T07:30:04Z

Damd: moved Unit Testing to Unit testing

{{Manual|ERT|(ert) Top}}
ERT is the unit test framework for developing Emacs lisp code. It is included as part of Emacs-24.1.

Talk:Main Page

2012-03-26T07:29:20Z

Damd: /* Info link markup */ Wrong link

I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)

== Markup Conventions==

=== Info link markup ===

Could/should we have some standard way of marking up links to Info sections? [[User:PhilHudson|PhilHudson]] 22:10, 24 March 2012 (EET)

:I've created the template [[Template:Manual]] as a start. I've used it a couple of times in [[Keyboard macros]], for reference. [[User:Damd|damd]] 19:59, 25 March 2012 (EEST)
:: I have introduced [[Template:Variable]], [[Template:Command]], [[Template:Function]] and also improved upon your template for [[Template:Manual]]. {{unsigned|101.63.150.116}}
:::I'm afraid your changes to the Manual template broke a few things, e.g. [[Unit testing]]. Could you take a look at that? [[User:Damd|damd]] 10:28, 26 March 2012 (EEST)

=== Wikipedia linking convention ===

Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)

=== EmacsWiki linking convention ===

Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)

=== Key sequences ===

Should we have a convention for marking up key sequences? I already see `C-x a` and <code>C-x a</code>
[[User:GregLucas|GregLucas]] 17:13, 25 March 2012 (EEST)

:+1 for any convention, I favor the latter over the former (but I'm using the former since that matches the first samples I encountered). [[User:PhilHudson|PhilHudson]] 17:23, 25 March 2012 (EEST)

:I think <code>C-x a</code> is better because it adds semantics to the text which web browsers understand. It's basically more accessible than `C-x a`. I'd like it if we could make a plugin for MediaWiki which allows us to use `C-x a` or `C-x a', with an apostrophe at the end, to ''become'' <code>C-x a</code>, since they're both pretty common notations. I think `this' notation is especially common in Emacs. [[User:Damd|damd]] 20:02, 25 March 2012 (EEST)

== Describing Modes and Packages ==

=== Naming Conventions ===

I'd like to suggest *not* suffixing (links to) modes with "-mode". Thus: "org" not "org-mode". For consistency I've been adding links titled "org-mode" until now, since that one was already created when I started. [[User:PhilHudson|PhilHudson]] 22:09, 24 March 2012 (EET)

:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]

:I actually disagree. E.g. [[Java]] could be a page describing the different Java capabilities of Emacs, with links to the different JavaScript modes. This is especially true for [[JavaScript]], where the [[js-mode]] shipped with the latest Emacs is completely different from the other widely used [[js2-mode]] by Yegge. [[User:Damd|Damd]] 18:20, 25 March 2012 (EEST)

::Hm, good point about disambiguation... I still like the idea of using "titles" vs "commands", though. E.g. a [[Java]] page describing the built-in support (Java Mode) and then linking to articles on related packages (JDEE, etc) and why you might consider them instead. [[User:GregLucas|GregLucas]] 19:32, 25 March 2012 (EEST)

:::How would we handle e.g. [[Haskell]]? Emacs doesn't ship with any Haskell mode as far as I know... [[User:Damd|damd]] 19:58, 25 March 2012 (EEST)

=== Built-ins vs Add-ons ===

An article on a mode/package should indicate whether it is part of the Emacs distribution. When there is a list of packages, maybe we group the built-in ones first and then the add-ons?
[[User:GregLucas|GregLucas]] 00:53, 25 March 2012 (EET)

Good idea. [[User:PhilHudson|PhilHudson]] 17:25, 25 March 2012 (EEST)

== Template for mode-with-github-source pages? ==

Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)

== Issues ==

=== FIXME Enable Wikimedia markup help pages ===

The "Editing Help" link goes to a virgin page, not the full help page.

== Syntax highlighting ==

Could we install a MediaWiki plugin which lets us do proper syntax highlighting of different languages? [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi] looks like a good alternative. [[User:Damd|damd]] 20:07, 25 March 2012 (EEST)

Talk:Main Page

2012-03-26T07:28:45Z

Damd: /* Markup Conventions */

I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)

== Markup Conventions==

=== Info link markup ===

Could/should we have some standard way of marking up links to Info sections? [[User:PhilHudson|PhilHudson]] 22:10, 24 March 2012 (EET)

:I've created the template [[Template:Manual]] as a start. I've used it a couple of times in [[Keyboard macros]], for reference. [[User:Damd|damd]] 19:59, 25 March 2012 (EEST)
:: I have introduced [[Template:Variable]], [[Template:Command]], [[Template:Function]] and also improved upon your template for [[Template:Manual]]. {{unsigned|101.63.150.116}}
:::I'm afraid your changes to the Manual template broke a few things, e.g. [[ERT]]. Could you take a look at that? [[User:Damd|damd]] 10:28, 26 March 2012 (EEST)

=== Wikipedia linking convention ===

Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)

=== EmacsWiki linking convention ===

Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)

=== Key sequences ===

Should we have a convention for marking up key sequences? I already see `C-x a` and <code>C-x a</code>
[[User:GregLucas|GregLucas]] 17:13, 25 March 2012 (EEST)

:+1 for any convention, I favor the latter over the former (but I'm using the former since that matches the first samples I encountered). [[User:PhilHudson|PhilHudson]] 17:23, 25 March 2012 (EEST)

:I think <code>C-x a</code> is better because it adds semantics to the text which web browsers understand. It's basically more accessible than `C-x a`. I'd like it if we could make a plugin for MediaWiki which allows us to use `C-x a` or `C-x a', with an apostrophe at the end, to ''become'' <code>C-x a</code>, since they're both pretty common notations. I think `this' notation is especially common in Emacs. [[User:Damd|damd]] 20:02, 25 March 2012 (EEST)

== Describing Modes and Packages ==

=== Naming Conventions ===

I'd like to suggest *not* suffixing (links to) modes with "-mode". Thus: "org" not "org-mode". For consistency I've been adding links titled "org-mode" until now, since that one was already created when I started. [[User:PhilHudson|PhilHudson]] 22:09, 24 March 2012 (EET)

:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]

:I actually disagree. E.g. [[Java]] could be a page describing the different Java capabilities of Emacs, with links to the different JavaScript modes. This is especially true for [[JavaScript]], where the [[js-mode]] shipped with the latest Emacs is completely different from the other widely used [[js2-mode]] by Yegge. [[User:Damd|Damd]] 18:20, 25 March 2012 (EEST)

::Hm, good point about disambiguation... I still like the idea of using "titles" vs "commands", though. E.g. a [[Java]] page describing the built-in support (Java Mode) and then linking to articles on related packages (JDEE, etc) and why you might consider them instead. [[User:GregLucas|GregLucas]] 19:32, 25 March 2012 (EEST)

:::How would we handle e.g. [[Haskell]]? Emacs doesn't ship with any Haskell mode as far as I know... [[User:Damd|damd]] 19:58, 25 March 2012 (EEST)

=== Built-ins vs Add-ons ===

An article on a mode/package should indicate whether it is part of the Emacs distribution. When there is a list of packages, maybe we group the built-in ones first and then the add-ons?
[[User:GregLucas|GregLucas]] 00:53, 25 March 2012 (EET)

Good idea. [[User:PhilHudson|PhilHudson]] 17:25, 25 March 2012 (EEST)

== Template for mode-with-github-source pages? ==

Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)

== Issues ==

=== FIXME Enable Wikimedia markup help pages ===

The "Editing Help" link goes to a virgin page, not the full help page.

== Syntax highlighting ==

Could we install a MediaWiki plugin which lets us do proper syntax highlighting of different languages? [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight GeSHi] looks like a good alternative. [[User:Damd|damd]] 20:07, 25 March 2012 (EEST)

Template:Unsigned

2012-03-26T07:28:18Z

Damd: Created page with "<small>— Preceding unsigned comment added by {{{1}}} (talk • contribs) {{{2|}}}</small>"

<small>— Preceding unsigned comment added by [[User:{{{1}}}|{{{1}}}]] ([[User talk:{{{1}}}|talk]] • [[Special:Contributions/{{{1}}}|contribs]]) {{{2|}}}</small>

Feed reading

2012-03-25T17:34:04Z

Damd: Adding Newsticker to list.

'''Feed reading''' in Emacs can be achieved in many different ways.

== Modes ==
These modes are effectively in-Emacs applications:

* [[Newsticker]]
* [[Gnus]]

Category:Programming

2012-03-25T17:32:06Z

Damd: Created page with "Pages in this category describe anything related to programming in Emacs."

Pages in this category describe anything related to programming in Emacs.

Python

2012-03-25T17:31:31Z