https://wikemacs.org/api.php?action=feedcontributions&user=Holocronweaver&feedformat=atomWikEmacs - User contributions [en]2024-03-19T11:44:47ZUser contributionsMediaWiki 1.35.14https://wikemacs.org/index.php?title=Main_Page&diff=50927Main Page2021-04-12T05:31:29Z<p>Holocronweaver: </p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 27|Emacs-27.2]] released on Mar 25th, 2021. The precedent is [[GNU Emacs 26|Emacs-26.3]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50921Main Page2020-12-13T22:07:09Z<p>Holocronweaver: </p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 27|Emacs-27.1]] released on Aug 10th, 2020. The precedent is [[GNU Emacs 26|Emacs-26.3]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Org&diff=50919Org2020-08-15T03:35:16Z<p>Holocronweaver: readme to README</p>
<hr />
<div>{{Package<br />
|name=Org,Org-Mode<br />
|description=GTD and document authoring package/markup language<br />
|author= Carsten Dominik<br />
|maintainer=Bastien Guerry<br />
|source=http://orgmode.org/w/org-mode.git<br />
|in_emacs=yes (likely be out of date)<br />
|Development status=active<br />
|website=http://orgmode.org<br />
}}<br />
<br />
'''Org''' is an Emacs mode for keeping notes, maintaining TODO lists,<br />
project planning, outlining, and authoring with a fast and effective<br />
plain-text system. Org Mode is simple enough to start using right<br />
away, but provides tons of advanced features to support a wide variety<br />
of tasks and workflows.<br />
<br />
Org-Mode is distributed with Emacs (since Emacs 22.2). This project is<br />
under active development and new releases are often available.<br />
<br />
=== Features ===<br />
<br />
* Simple plain text markup for hierarchical documents.<br />
* Built-in table editor: easily format tables and work with spreadsheets in plain text.<br />
* Extensible hyperlinking: create cross-references, link to external resources, and more.<br />
* Capture system: create templates to quickly capture and file notes and tasks. <br />
* Sequences of TODO-style keywords for task progress tracking.<br />
* Tags, priorities and properties to categorize, sort, filter, and search.<br />
* Custom project views using Org's Agenda.<br />
* Convenient date/time handling for timestamps, deadlines, and scheduling.<br />
* Clock support to track time spent on projects.<br />
* Export from plain-text to a variety of formats (HTML, LaTeX, DocBook, etc).<br />
* Embedded source blocks: edit code blocks in-line with the appropriate mode. Execute code blocks to generate content. Org can even be used for [http://en.wikipedia.org/wiki/Literate_programming literate programming].<br />
* Mobile support providing a subset of Org capabilities on iOS and Android devices.<br />
<br />
== External Links ==<br />
The Org-Mode project maintains excellent documentation and has an active community.<br />
<br />
* [http://orgmode.org/ Org Project]<br />
* [http://orgmode.org/org.html Documentation]<br />
* [http://orgmode.org/w/org-mode.git Source Repository (git)]<br />
* [http://orgmode.org/worg/ Worg, the Org Community!]<br />
* [http://doc.norang.ca/org-mode.html Organize your life in plain text!]<br />
<br />
[[Category:Org]][[Category:Document authoring]][[Category:Markup languages]][[Category:Built-in Package]][[Category:Popular Package]] [[Category:GTD]]<br />
[[Category:Desktop Management]][[Category:Organizer]]<br />
<br />
== Extensions ==<br />
<br />
=== Org-ql: a query language for Org files ===<br />
<br />
[https://github.com/alphapapa/org-ql org-ql] is a query language for Org files. It offers two syntax styles: Lisp-like sexps and search engine-like keywords.<br />
<br />
[[File:Org-ql-search.gif]]<br />
<br />
=== Org-wiki ===<br />
<br />
[https://github.com/caiorss/org-wiki org-wiki] allows to easily create links and browse them (helm integration).<br />
<br />
=== Find files and headlines anywhere, anytime, by indexing them in a database ===<br />
<br />
This is the approach taken by John Kitchin who handles thousands of org files: http://kitchingroup.cheme.cmu.edu/blog/2017/01/03/Find-stuff-in-org-mode-anywhere/<br />
<br />
Admittedly its current approach is a bit tedious since one has to write sql queries, also there is not all the possible features yet, like an ignore pattern.<br />
<br />
=== Search rapidly everywhere: helm-org-rifle ===<br />
<br />
[https://github.com/alphapapa/helm-org-rifle helm-org-rifle]: It searches rapidly through my Org files, quickly bringing me the information I need to defeat the enemy.<br />
<br />
This package is a continuation of the fantastic org-search-goto/org-search-goto-ml packages, now with Helm support. It searches both headings and contents of entries in Org buffers, and it displays entries that match all search terms, whether the terms appear in the heading, the contents, or both. Matching portions of entries’ contents are displayed with surrounding context and grouped by buffer to make it easy to acquire your target.<br />
<br />
=== Generate an inline table of contents (toc) for github READMEs ===<br />
<br />
That's possible with [https://github.com/snosov1/toc-org toc-org], available in melpa. We set an heading as '':TOC:'' and then we can call '''M-x toc-org-insert-toc''' or make it update the toc at every file save.<br />
<br />
=== Preview on save ===<br />
<br />
[https://github.com/lujun9972/org-preview-html org-preview] (in MELPA) is an Emacs minor mode for org mode that automatically uses the built-in eww browser to preview the current org file. The preview is updated every time the org file is saved.<br />
<br />
=== Retrieve a web page content and display it as org mode content ===<br />
<br />
See [https://github.com/alphapapa/org-web-tools org-web-tools] (in MELPA, for Emacs 25.1 or later). <br />
<br />
This file contains library functions and commands useful for retrieving web page content and processing it into Org-mode content.<br />
<br />
For example, you can copy a URL to the clipboard or kill-ring, then run a command that downloads the page, isolates the “readable” content with eww-readable, converts it to Org-mode content with Pandoc, and displays it in an Org-mode buffer. Another command does all of that but inserts it as an Org entry instead of displaying it in a new buffer.<br />
<br />
=== Org-sidebar, chronological list of scheduled and deadlined tasks ===<br />
<br />
See [https://github.com/LispCookbook/cl-cookbook/pull/175 org-sidebar]. At the top is a chronological list of scheduled and deadlined tasks in the current buffer (similar to the Org agenda ,but without all its features), and below that is a list of all other non-done to-do items. If the buffer is narrowed, the sidebar only shows items in the narrowed portion; this allows seeing an overview of tasks in a subtree.<br />
<br />
It relies on two packages not in Melpa.<br />
<br />
=== Organice: use org-mode from a smartphone or browser ===<br />
<br />
[https://github.com/200ok-ch/organice organice] is "an implementation of Org mode without the dependency of Emacs - built for mobile and desktop browsers".<br />
<br />
And indeed. Organice is a front-end application, which uses either Dropbox, Google Drive or WebDAV as back-end storage.<br />
<br />
[[File:Organice.png]]<br />
<br />
== See also ==<br />
<br />
=== Deft, to browse and edit directories of plain text notes ===<br />
<br />
[http://jblevins.org/projects/deft/ Deft], an Emacs mode for quickly browsing, filtering, and editing directories of plain text notes, inspired by Notational Velocity. It can be a way to leverage the process of taking notes in several org files.<br />
<br />
=== Use Recoll, the desktop database from Emacs ===<br />
<br />
See [http://oremacs.com/2015/07/27/counsel-recoll/ this blog post].<br />
<br />
=== Outshine, to bring the look and feel of Org mode outside of the Org major mode ===<br />
<br />
See [https://github.com/alphapapa/outshine outshine-mode].</div>Holocronweaverhttps://wikemacs.org/index.php?title=ESS&diff=50917ESS2020-07-03T20:24:48Z<p>Holocronweaver: </p>
<hr />
<div>'''ESS'' (The Emacs Speaks Statistics) ([http://ess.r-project.org/ ESS]) mode provides a tight integration of the powerful [http://www.r-project.org/ GNU R] statistics system into Emacs. In addition, ESS has support for [http://www.sas.com/ SAS], BUGS (Bayesian Uniform Gibbs Sampler) and JAGS (Just another Gibbs Sampler). Finally, it also provides an equally tight integration with S-plus, direct descendant of the S language created by John Chambers at Bell Labs. It comes with an editing mode for .R files providing syntax highlighting as well as an interactive R console based on the Emacs comint mode.<br />
<br />
ESS also provides (along with [[AucTex]]) a superior editing environment for noweb files, (typically files with an Rnw extension). These files mix R code and LaTeX text and markup and can be used to facilitate reproducible research. Important commands for Sweave mode are M-n-s, which runs all the code-blocks in a Rnw file, M-n-w which copies the code chunk at point, and M-n-k, which kills the code chunk at point. <br />
<br />
ESS also provides an interface to the R help system. Help for any topic can be accessed using C-c C-v and typing the name of a function or operator. A new buffer containing the source code for the function at point can be created using C-c C-d. <br />
<br />
[[Org]] Mode can also be used to work with [http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html R source code blocks].<br />
<br />
[[Category:Statistics]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=ESS&diff=50916ESS2020-07-03T20:24:39Z<p>Holocronweaver: </p>
<hr />
<div>'''ESS'' (The Emacs Speaks Statistics) ([http://ess.r-project.org/ ESS]) mode provides a tight integration of the powerful [http://www.r-project.org/ GNU R] statistics system into Emacs. In addition, ESS has support for [http://www.sas.com/ SAS], BUGS (Bayesian Uniform Gibbs Sampler) and JAGS (Just another Gibbs Sampler). Finally, it also provides an equally tight integration with S-plus, direct descendant of the S language created by John Chambers at Bell Labs. It comes with an editing mode for .R files providing syntax highlighting as well as an interactive R console based on the Emacs comint mode.<br />
<br />
ESS also provides (along with [[AucTex]]) a superior editing environment for noweb files, (typically files with an Rnw extension). These files mix R code and LaTeX text and markup and can be used to facilitate reproducible research. Important commands for Sweave mode are M-n-s, which runs all the code-blocks in a Rnw file, M-n-w which copies the code chunk at point, and M-n-k, which kills the code chunk at point. <br />
<br />
ESS also provides an interface to the R help system. Help for any topic can be accessed using C-c C-v and typing the name of a function or operator. A new buffer containing the source code for the function at point can be created using C-c C-d. <br />
<br />
[[Org]] Mode can also be used to work with [http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html R source code blocks].<br />
<br />
[[Category:Statistics]]<br />
<br />
test</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=50909User:Holocronweaver2020-02-24T00:00:47Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* ✔ add HTTPs support<br />
* add multi-page nuke support to remove historical spam<br />
* track page traffic to prioritize edits<br />
* fix RSS feed<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the homeless pet captcha, has been closed down in Dec 2014 - hopefully something similar will sprout up<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]<br />
<br />
[[Category:WikEmacs Contributor]]<br />
<br />
=Test=</div>Holocronweaverhttps://wikemacs.org/index.php?title=User_talk:Holocronweaver&diff=50844User talk:Holocronweaver2019-02-25T21:03:31Z<p>Holocronweaver: /* Report spam */</p>
<hr />
<div>Hello, Holocronweaver, I am new to WikEmacs. Any chance we could get http://wikemacs.org/index.php/Keyboard_macros protected?<br />
<br />
: Done. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 21:00, 21 November 2013 (EST)<br />
<br />
== What is the policy about non-English articles? ==<br />
<br />
I found this page in Chinese:<br />
<br />
[[Keyboard_macros]]<br />
<br />
I'm not interested in running it through a translator and seeing what's usable, so I would delete it without mercy.<br />
<br />
I did check [[WikEmacs:Guidelines]], but didn't see any indication of a policy on this matter.<br />
<br />
Are there guidelines about non-English contributions?<br />
<br />
Thanks.<br />
<br />
: Sorry for slow response. I can actually read some Chinese, and what is posted there is spam for a Chinese biotech company. It is useless, so I reverted it. I did not realize we had a Guidelines page, good to know! I will look into adding multi-language support, but it may take a couple months. Until then, if you come across non-English text you think is worth preserving, copy it here and mention the source article. I will get it added to its appropriate language page once support is added. Thanks! --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 20:17, 24 January 2016 (EST)<br />
<br />
== Report spam ==<br />
<br />
Hi, I just found [[User:Bythirdparty]] created a lot [[Special:Contributions/Bythirdparty|spam pages]]. Please delete these.—<span style="color:blue ; text-shadow: 0pt 1px 2px blue; font-style:italic">[[User: Wi24rd|wi24rd]]</span> <sup>[[User talk:wi24rd|<span style="color:purple; font-style:italic">leave a comment</span>]]</sup> 10:52, 22 February 2019 (EST)<br />
<br />
: Buh-leeted! Thanks for the report. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 16:03, 25 February 2019 (EST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=50828User:Holocronweaver2018-09-20T20:52:59Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* ✔ add HTTPs support<br />
* add multi-page nuke support to remove historical spam<br />
* track page traffic to prioritize edits<br />
* fix RSS feed<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the homeless pet captcha, has been closed down in Dec 2014 - hopefully something similar will sprout up<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]<br />
<br />
[[Category:WikEmacs Contributor]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=50827User:Holocronweaver2018-09-20T20:47:00Z<p>Holocronweaver: /* TODO */</p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* ✔ add HTTPs support<br />
* fix RSS feed<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the homeless pet captcha, has been closed down in Dec 2014 - hopefully something similar will sprout up<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]<br />
<br />
[[Category:WikEmacs Contributor]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Python&diff=50805Python2018-05-09T14:47:35Z<p>Holocronweaver: minor style improvement</p>
<hr />
<div>How can we turn Emacs as full featured Python IDE? How to use Emacs for data science? Many packages are explained below. You don't have to install all of them one by one, see the all-in-one solutions, like Elpy, [http://wikemacs.org/wiki/Starter_Kits starter kits] and the [https://spacemacs.org/layers/+lang/python/README.html Spacemacs] layer.<br />
<br />
An important library you'll want to get familiar with is [https://jedi.readthedocs.io/en/latest/ Jedi], an autocompletion and analysis library for Python. It helps at autocompletion, finding definitions, showing documentation, etc. Elpy makes good use of it.<br />
<br />
We also have Rope that allows cross-project refactoring and smaller ones (change the method signature,…). Again Elpy bases on it and other packages like emacs-traad make it easy to install and use.<br />
<br />
See also [[Django]] support.<br />
<br />
== Default modes ==<br />
<br />
There are a number of python modes for Emacs.<br />
fgallina's [https://github.com/fgallina/python.el python.el] is the python.el included in Emacs 24.2 and onwards.<br />
<br />
== All-in-one solutions ==<br />
<br />
=== emacs-for-python ===<br />
<br />
'''emacs-for-python''' is a bundle of the above modes (and more), and it's an easy way to turn Emacs into a Python IDE.<br />
<br />
[https://github.com/gabrielelanaro/emacs-for-python/ emacs-for-python at github]<br />
<br />
=== Elpy ===<br />
<br />
'''Elpy''' is a collection of elisp packages for Python too.<br />
<br />
https://github.com/jorgenschaefer/elpy/wiki/Features<br />
<br />
It permits, among others, to:<br />
<br />
* refactor code (using rope),<br />
* send a region or a buffer to a python interpreter,<br />
* run unit tests, run the test the cursor is in, with a test runner of choice (django, pytest, …),<br />
* jump to a symbol definition (elpy-goto-definition),…<br />
<br />
and of course<br />
<br />
* on-the-fly checks with flymake,<br />
* code completion with company-mode and either rope or jedi,<br />
* on the fly code helper with eldoc (and rope or jedi), <br />
* code navigation,<br />
* change of virtual environment inside Emacs (pyvenv), etc<br />
<br />
=== EMP: EMacs Python ===<br />
<br />
The goal of '''emp''' is to take all the best development components available for Python, and combine it conveniently under Emacs. It builds on top of elpy, and provides even more bindings.<br />
<br />
https://kootenpv.github.io/2016-01-01-emacs-python<br />
<br />
=== Emacs-bootstrap ===<br />
<br />
[http://emacs-bootstrap.com/ Emacs-bootstrap] is a website where you can select a few programming languages, some options, and have it generate a full .emacs.d folder for you.<br />
<br />
== Refactoring ==<br />
<br />
=== rope & ropemacs ===<br />
<br />
==== Presentation ====<br />
<br />
'''rope''' is a library for refactoring and manipulating Python code, '''pymacs''' is an interface between emacs lisp and python, and '''{{ModeLink|ropemacs}}''' is an Emacs interface to the rope library which uses rope and pymacs.<br />
<br />
If you do some search and replace of code objects in your code and find it sometimes tricky, and/or you need to do it in more than one file, then you should consider a good tool of refactoring.<br />
<br />
But Rope can do more than this simple example, it can:<br />
<br />
* Rename anything<br />
* Extract method/local variable <br />
* Change method signature <br />
* Perform cross-project refactorings<br />
* Support Mercurial, GIT, Darcs and SVN in refactorings <br />
<br />
Rope can also help IDE's with: <br />
<br />
* Auto-completion<br />
* Finding definition location<br />
* Getting pydoc<br />
* Finding occurrences<br />
* Organizing imports (removing unused and duplicate imports and sorting them)<br />
* Generating python elements <br />
<br />
==== Installation ====<br />
<br />
Note: see also emacs-traad below that has an easy installation process.<br />
<br />
===== With el-get =====<br />
<br />
So an easy way is to use an [[el-get]] recipe: '''M-x el-get-install ropemacs'''. It installs and build Pymacs, rope and ropemacs. The difference from the solution using pip is that it setups the Emacs side of Pymacs correctly.<br />
<br />
===== Manually =====<br />
<br />
You can follow the instructions as given [http://stackoverflow.com/a/22496541/4018217 here] ,if you don't want to use marmalade you can use the following instructions .<br />
<br />
sudo pip install rope ropemacs<br />
<br />
As of February 2014 you can't install Pymacs via pip, therefore:<br />
<br />
git clone http://github.com/pinard/pymacs<br />
cd pymacs<br />
make check<br />
sudo make install<br />
<br />
make check ensures the prerequisites. sudo make install puts Pymacs module in Python local modules path, usually /usr/local/lib/python2.7/dist-packages/. People generally frown upon make install, because if you lose the Makefile, it can become hard to cleanly uninstall. But you shouldn't fear it, as pip uses the same directory, so pip uninstall pymacs will work.<br />
<br />
'''After you do the make install of pymacs do not delete the folder.Copy the file pymacs.el to ~/.emacs.d/site-lisp/'''<br />
<br />
Now add path of pyamcs.el to your ~/.emacs file,using this code:<br />
(setq emacs-config-path "~/.emacs.d/") <br />
(setq base-lisp-path "~/.emacs.d/site-lisp/")<br />
(setq site-lisp-path (concat emacs-config-path "/site-lisp"))<br />
(defun add-path (p)<br />
(add-to-list 'load-path (concat base-lisp-path p)))<br />
(add-path "")<br />
(add-to-list 'load-path "~/.emacs.d")<br />
<br />
You can now lazily load ropemacs or load it at runtime.For lazy evaluation add this to your .emacs file:<br />
(defun load-ropemacs ()<br />
"Load pymacs and ropemacs"<br />
(interactive)<br />
(require 'pymacs)<br />
(pymacs-load "ropemacs" "rope-")<br />
;; Automatically save project python buffers before refactorings<br />
(setq ropemacs-confirm-saving 'nil)<br />
)<br />
(global-set-key "\C-xpl" 'load-ropemacs)<br />
<br />
use c-xpl to load ropemacs.Read more about it [https://github.com/python-rope/ropemacs#setting-up here]<br />
<br />
=== Rope & traad ===<br />
<br />
[https://github.com/abingham/traad Traad] is a client-server approach to using the rope Python refactory library. It involves two basic components:<br />
* A HTTP server exposing the rope API via JSON, and<br />
* Client libraries for talking to the server<br />
Since rope is written in Python, any tool that wants to use rope needs to either embed Python, or it needs to find a way to communicate with a Python process running rope. The embedding approach is difficult if the target environment is not written in Python, and it also faces challenges when dealing with more than one Python version.<br />
<br />
So traad aims to simplify communication with rope running in an independent process. HTTP communication and JSON data handling is well supported in many, many languages, so any environment that wants to use rope should be able to easily communicate with traad.<br />
<br />
==== emacs-traad, easy installation and use ====<br />
<br />
[https://github.com/abingham/emacs-traad emacs-traad] (simply traad in melpa) makes it very easy to install traad, and thus rope. Install traad from melpa and then '''M-x traad-install-server'''. Then start a connection with traad-open and enjoy. Furthermore it installs traad in its own virtualenv, so it won't clutter your current virtualenv, and you don't have to re-install it in every project.<br />
<br />
==== usage ====<br />
<br />
It is possible to remove a method's argument, normalize arguments, see the occurrences of a method, organize imports, some more python refactoring, and also see the history of traad changes.<br />
<br />
=== Other Python "refactoring" tools ===<br />
<br />
==== Projectile - replace in project ====<br />
<br />
This is not specific to Python but is very helpful anyway. [[Projectile]] has a function '''projectile-replace''' which interactively offers to replace all occurrences of a term in all the files of the project. So it's handy to rename a method.<br />
<br />
==== Iedit - replace occurences of a symbol ====<br />
<br />
[https://github.com/victorhge/iedit Iedit] isn't specific to Python and isn't a "real" "intelligent" refactoring, but it helps editing similar portions of text in the current buffer, with highlighting and simultaneous editing, like multicursors. Go on a variable you want to rename and call '''iedit''' (bound to '''C-;'''). You can restrict to the current method with a 0 prefix argument: '''C-u 0 M-x iedit'''. You can use '''C-\'''' (control quote) to only show the lines that will be edited.<br />
<br />
<br />
==== Red4e - change the method signature, add decorators ====<br />
<br />
[https://gitlab.com/vindarel/redbaron4emacs/ red4e] (not a package) is a little utility, considered a proof of concept, that helps at modifying the current method signature: <br />
<br />
* '''add a decorator''', remove one, automatically adding or removing "self" for a staticmethod,<br />
* '''add an argument''' (and rename it inside the method body), remove an argument, add the couple "*args, **kwargs", <br />
* '''rename/copy/comment/kill the current method''' (and rename it in the project too), <br />
* quickly go to another method (with imenu), <br />
* toggle arguments on '''one or multiple lines''',<br />
* and more, to be continued.<br />
<br />
It uses under the hood (mostly, not everywhere) the redbaron python library that allows to manipulate an FST (Full Syntax Tree).<br />
<br />
==== Pygen - code generation ====<br />
<br />
See [https://github.com/JackCrawley/pygen pygen]. Unmaintained.<br />
<br />
=== Refactor with Elpy ===<br />
<br />
See Elpy's documentation: http://elpy.readthedocs.io/en/latest/ide.html?highlight=django#refactoring<br />
<br />
One can refactor code (with rope), format code, edit all the occurences of the symbol at point simultaneously, and fix imports.<br />
<br />
== Auto-Completion ==<br />
<br />
<br />
=== Jedi ===<br />
<br />
Jedi.el is a Python auto-completion package for Emacs. It aims at helping your Python coding in a non-destructive way. It also helps you to find information about Python objects, such as docstring, function arguments and code location.<br />
<br />
Jedi is simple to install and it works out of the box.<br />
<br />
See screenshots and get the full documentation : http://tkf.github.io/emacs-jedi/released/<br />
<br />
Jedi's official page: http://jedi.jedidjah.ch/en/latest/<br />
<br />
==== Installation ====<br />
<br />
Install Jedi.el via el-get, Marmalade or MELPA (see install for more info) and add this to your Emacs configuration:<br />
(add-hook 'python-mode-hook 'jedi:setup)<br />
(setq jedi:setup-keys t) ; optional<br />
(setq jedi:complete-on-dot t) ; optional<br />
<br />
or call M-x jedi:setup<br />
<br />
''Note'': it's nice to use it in a python interpreter inside emacs :)<br />
<br />
=== Anaconda ===<br />
<br />
'''Anaconda-mode''' is a mode for '''code navigation, documentation lookup''' and '''completion''' for Python.<br />
<br />
It runs on '''emacs 24.3''' with python >= 2.6. <br />
<br />
It provides:<br />
<br />
* context-sensitive code completion for Python<br />
* jump to definition<br />
* find references<br />
* view documentation<br />
* virtualenv management<br />
<br />
The package is available in [[MELPA]]. For more information, [https://github.com/proofit404/anaconda-mode read its documentation].<br />
<br />
== Code Checker ==<br />
<br />
=== Flymake and Flycheck ===<br />
<br />
[[Flymake]] (in Emacs) is a on-the-fly syntax checker for Emacs. <br />
We can use it with [[flycheck]] (in melpa), that aims at being a replacement.<br />
<br />
To run pep8, pylint, pyflakes and unit-tests (with nose), you can be interested in using [https://github.com/akaihola/flymake-python flymake-python].<br />
<br />
Don't forget about '''pylint''' too.<br />
<br />
[[File:flycheck-annotated.png]]<br />
<br />
=== MyPy checks ===<br />
<br />
With [https://github.com/SerialDev/mypy-mode mypy-mode] we get a compilation-mode based support for python 3.6+ type hints checks.<br />
<br />
As a side note, we can also get flycheck to work, at the same time as pylint, with:<br />
<br />
<source lang="elisp"><br />
(flycheck-define-checker<br />
python-mypy ""<br />
:command ("mypy"<br />
"--ignore-missing-imports" "--fast-parser"<br />
"--python-version" "3.6"<br />
source-original)<br />
:error-patterns<br />
((error line-start (file-name) ":" line ": error:" (message) line-end))<br />
:modes python-mode)<br />
<br />
(add-to-list 'flycheck-checkers 'python-mypy t)<br />
(flycheck-add-next-checker 'python-pylint 'python-mypy t)<br />
</source><br />
<br />
== Indexing sources: ctags, cscope, pycscope == <br />
<br />
Indexing sources allows you to do neat things, like going to the definition of a function or finding which functions are calling another one.<br />
<br />
Note that Elpy does the "go to definition" feature (elpy-goto-definition), without the need of indexing sources.<br />
<br />
=== etags, ctags ===<br />
<br />
'''Etags''' (Exuberant Ctags) generates an index (or tag) file of language objects found in source files that allows these items to be quickly and easily located by a text editor or other utility. A tag signifies a language object for which an index entry is available (or, alternatively, the index entry created for that object). Etags is a multilingual implementation of '''ctags'''.<br />
<br />
The primary use for the tags files is looking up class/method/function/constant/etc declaration/definitions. Cscope is more powerful (see below).<br />
<br />
==== usage ====<br />
<br />
Generate the tags with this command at the root of your project:<br />
<br />
find . -name "*.py" -print | etags -<br />
<br />
it creates the file TAGS.<br />
<br />
Note that projects like [[Projectile]] or [[Helm]] provide an integrated use of etags (finding one, re-generating the index, etc).<br />
<br />
=== cscope ===<br />
<br />
'''cscope''' is a much more powerful beast. While it operates on more or less the same principle (generating a file of useful metadata) it allows you do some fancier things like find all references to a symbol, see where a function is being invoked, etc.+ (you can find definitions as well). <br />
<br />
It was originally designed for C and C++, but thanks to version 0.3 of '''pycscope''', pythonistas can make use of it.<br />
<br />
==== usage ====<br />
<br />
The following commands should get you running: <br />
<br />
apt-get install cscope<br />
pip install pycscope<br />
# in project base dir:<br />
find . -name '*.py' > cscope.files<br />
cscope -R <br />
<br />
now install the '''xcscope''' emacs package with [[ELPA]] and require it: <br />
(require 'xcscope)<br />
<br />
When done, you can either enable the mode with '''cscope-minor-mode''' (which will add a menu you are free to explore) or call some functions like {{Command|cscope-find-global-definition}}, {{Command|cscope-find-functions-calling-this-function}}, etc.<br />
<br />
==== Interactivity with helm-cscope ====<br />
<br />
You can do all that interactively with [https://github.com/alpha22jp/helm-cscope.el helm-cscope] (in melpa): when you are on symbol, just call {{Command|helm-cscope-find-global-definition}} (for example) and enjoy the nice interactive interface.<br />
<br />
== Running tests ==<br />
<br />
Elpy has commands to run either all tests of the current buffer or only the test we are on. It supports launchers for '''Django''' (thus using "manage.py test"), '''pytest''' and '''nose'''. See http://elpy.readthedocs.io/en/latest/ide.html?highlight=django#testing<br />
<br />
If you wish to modify the way it runs test, set the following variable:<br />
<br />
<source lang="lisp"><br />
(setq elpy-test-<django, nose, pytest>-runner-command '("./manage.py" "test"))<br />
</source><br />
<br />
=== A Hydra to choose what tests to run, navigate errors and switch to the console ===<br />
<br />
See this snippet: https://github.com/abo-abo/hydra/wiki/Elpy<br />
<br />
<br />
=== Running Make, with completion of commands ===<br />
<br />
It can be handy to call a Makefile target from wherever we are in a project, and even more handy with fuzzy completion of the targets. This is easily done with [https://github.com/abo-abo/helm-make helm-make]. It is also included in [[Django]] mode, which does the same for management commands.<br />
<br />
[[File:Make-helm.png]]<br />
<br />
== Debugging ==<br />
<br />
Well, let's start with the debuggers documentation:<br />
<br />
* [https://docs.python.org/3/library/pdb.html pdb doc]<br />
* [https://pypi.python.org/pypi/pdbpp/ pdb++] has a few more commands<br />
* [https://pypi.python.org/pypi/ipdb ipdb] to make use of ipython (aka jupyter)<br />
<br />
=== Ipdb, ipython debugger ===<br />
<br />
If you call ipdb, the execution will stop and give a nice ipython-looking prompt.<br />
Just add the line <br />
<br />
import ipdb; ipdb.set_trace()<br />
<br />
Now you can use the usual commands: '''c''' to continue the execution, '''n''' to execute the next one, '''s''' to step into the next function call, '''l''' to list the source code, '''!''' to execute a statement in the current context, etc.<br />
<br />
Note: if you like IPython/Jupyter, look at the [https://github.com/millejoh/emacs-ipython-notebook Emacs IPython Notebook].<br />
<br />
Note: You can use [[yasnippet]] to quickly enter this sentence, or just a simple function:<br />
<br />
<source lang="lisp"><br />
(defun python-add-breakpoint ()<br />
"Add a break point"<br />
(interactive)<br />
(newline-and-indent)<br />
(insert "import ipdb; ipdb.set_trace()")<br />
(highlight-lines-matching-regexp "^[ ]*import ipdb; ipdb.set_trace()"))<br />
</source><br />
<br />
You can use the following to highlight this line, and not forget it :<br />
<source lang="scheme"><br />
; Highlight the call to ipdb<br />
; src http://pedrokroger.com/2010/07/configuring-emacs-as-a-python-ide-2/<br />
(defun annotate-pdb ()<br />
(interactive)<br />
(highlight-lines-matching-regexp "import ipdb")<br />
(highlight-lines-matching-regexp "ipdb.set_trace()"))<br />
(add-hook 'python-mode-hook 'annotate-pdb)<br />
</source><br />
<br />
And just delete every breakpoints of the buffer:<br />
<source lang="list"><br />
(defun ipdb-cleanup ()<br />
(interactive)<br />
(save-excursion<br />
(replace-regexp ".*ipdb.set_trace().*\n" "" nil (point-min) (point-max))<br />
;; (save-buffer)<br />
))<br />
</source><br />
<br />
=== pdb track ===<br />
<br />
If you use emacs-for-python given above, you can track your source code while debugging with pdbtrack.<br />
<br />
A tool to use in a non-emacs terminal would be [https://pypi.python.org/pypi/pdbpp/ pdbpp]<br />
<br />
=== Realgud, a front end to many debuggers to stay in the source window ===<br />
<br />
[https://github.com/realgud/realgud Realgud] is a graphical front-end to many python debuggers. The goal is to call the debugger from within Emacs and manipulate it ('''c'''ontinue, '''n'''ext commands, setting breakpoints, etc) within the source window, with single key presses. We can also inspect variables with mouse clicks, set and clear breakpoints (from the source, with mouse clicks), evaluate expressions, etc.<br />
<br />
[[File:Realgud.png]]<br />
<br />
=== Redefine the code being run in the debugger session ===<br />
<br />
The tip in [http://wenshanren.org/?p=351 this article] makes use of the pdb feature to execute code in the context of the current stack frame with the "!" command (which can actually be omitted. See [https://docs.python.org/3/library/pdb.html the pdb doc]) and it uses an emacs package to make it much easier to write code blocks for the (i)pdb prompt (à la org-mode code blocks).<br />
<br />
=== M-x compile and breakpoints ===<br />
<br />
You may run your script from a real terminal, from emacs with M-x shell or with M-x compile. If you like the latter you'll notice that it hangs if you set breakpoints inside your code. The function below checks if your code has breakpoints and if so, it gives you the hand for the debugger prompt:<br />
<br />
<source lang="lisp"><br />
; thanks to https://masteringemacs.org/article/compiling-running-scripts-emacs (slightly modified)<br />
(defadvice compile<br />
(before ad-compile-smart activate)<br />
"Advises `compile' so it sets the argument COMINT to t if breakpoints are present in `python-mode' files"<br />
(when (derived-mode-p major-mode 'python-mode)<br />
(save-excursion<br />
(save-match-data (goto-char (point-min))<br />
(if (search-forward "ipdb.set_trace()"<br />
(point-max)<br />
t)<br />
(progn (ad-set-arg 1 t)<br />
(switch-to-buffer-other-window "*compilation*")))))))<br />
</source><br />
Now just run '''M-x compile''' as usual.<br />
<br />
== Documentation ==<br />
<br />
=== Insert Sphinx docstrings ===<br />
<br />
The package [https://github.com/naiquevin/sphinx-doc.el sphinx-doc] (on melpa) offers, with one shortuct, to insert ''or update'' Sphinx-like docstrings for the current method's arguments.<br />
<br />
<br />
=== Eldoc: argument list in the echo area ===<br />
<br />
Eldoc is a MinorMode which shows you, in the echo area, the argument list of the function call you are currently writing. It works out of the box for elisp editing and for modes that implement its support, such as python-mode. You just have to call '''eldoc-mode'''.<br />
<br />
To always enable it:<br />
<br />
(add-hook 'python-mode-hook 'eldoc-mode)<br />
<br />
=== Jedi: show the method signature, show documentation ===<br />
<br />
This pops up the function signature when you're between parentheses for a function call (not the default): '''M-x jedi:get-in-function-call'''.<br />
<br />
There is also '''M-x jedi:show-doc''' to show the docstring for the symbol at point in another window.<br />
<br />
See more in [https://jedi.readthedocs.io/en/latest/ the Jedi documentation].<br />
<br />
=== helm-pydoc ===<br />
<br />
'''helm-pydoc''' is a little utility that lets you interactively select a module you want read the doc and displays it in another buffer.<br />
<br />
=== pydoc linkification ===<br />
<br />
If you've ever used the emacs lisp documentation system, you may find that the pydoc is poorer in functionnalities:<br />
* there is no direct link to code source<br />
* there is no "back" button<br />
<br />
John Kitchin's pydoc aims at fixing that with more enhancements, like a bit of source fontification. See more at [http://kitchingroup.cheme.cmu.edu/blog/2014/12/20/A-new-mode-for-Python-documentation/ his presentation] and [https://github.com/jkitchin/jmax/blob/master/pydoc.el on github].<br />
<br />
=== info format ===<br />
<br />
Another way to read the python documentation is in the texinfo format. You'll need to install the package '''python-info''' [http://melpa.org/#/python-info on MELPA] and go through [https://bitbucket.org/jonwaltman/pydoc-info/ the installation process].<br />
<br />
== Datascience ==<br />
<br />
=== the Scimax starter kit ===<br />
<br />
See [https://github.com/jkitchin/scimax Scimax], a starter kit for scientists and engineers, for people interested in reproducible research and publishing. Scimax is just Emacs that has been configured extensively to make it act like we need it to for research documentation and publication. It provides a lot of customization of org-mode, improvements to bibliography, tools to send emails, manage a contacts database, evaluating code asynchronously, and more.<br />
<br />
=== Ipython / Jupyter notebooks ===<br />
<br />
You have [http://jupyter.org/ online Jupyter notebooks], also a [https://jupyter.org/qtconsole/ Qt console] and an [https://github.com/millejoh/emacs-ipython-notebook emacs ipython notebook] !<br />
<br />
Notebooks allow you to create and share documents that contain live code, equations, visualizations and explanatory text. Uses include: data cleaning and transformation, numerical simulation, statistical modeling, machine learning and much more. This is [https://nbviewer.jupyter.org/github/akittas/presentations/blob/master/pythess/func_py/func_py.ipynb an example of result]. You can [https://try.jupyter.org/ try it online].<br />
<br />
<br />
[[File:emacs-ipython.png||||the emacs ipython notebook, mixing and evaluating code, text and graphics]]<br />
<br />
=== lpy - eval a region, step through expressions ===<br />
<br />
[https://github.com/abo-abo/lpy lpy] is a little tool that offers to:<br />
<br />
* press '''e''' in the right position (before an expression) to eval it,<br />
* press '''j''' to go to the next expression<br />
<br />
and more ! It's a new tool in development (by a great developer, rest assured the doc will follow ! :p)<br />
<br />
You'll have to read its documented source. Lpy is actually is an attempt to implement a variant of [https://github.com/abo-abo/lispy lispy-mode]<br />
for Python. Unfortunately,<br />
Python isn't nearly as well-structured as LISP. But Python is<br />
ubiquitous, and the less powerful `lpy-mode' is better than nothing<br />
at all. The basic idea of `lpy-mode' is to increase the editing efficiency<br />
by binding useful navigation, refactoring and evaluation commands<br />
to unprefixed keys, e.g. "j" or "e". But only in certain point<br />
positions, so that you are still able to use uprefixed keys to<br />
insert themselves.<br />
Example, here "|" represents the point position:<br />
<br />
print |("2+2=%d" % (2 + 2))<br />
<br />
Here, if you press the key "e", the whole line will be evaluated<br />
and "2+2=4" will be printed in the Echo Area.<br />
<br />
=== Send the current paragraph to the REPL, go to the next paragraph ===<br />
<br />
<source lang="elisp"><br />
(defun my-python-para-send-and-step ()<br />
"Sends the current paragraph to the python REPL and goes to the next one"<br />
(interactive)<br />
(mark-paragraph)<br />
(python-shell-send-region)<br />
(forward-paragraph))<br />
</source><br />
<br />
=== Send code to the REPL (isend-mode, eval-in-repl) ===<br />
<br />
This is actually a default feature of python.el. See its menu to send a line or a region to the repl.<br />
<br />
Besides, [https://github.com/ffevotte/isend-mode.el isend-mode] (in MELPA) works with many languages and REPLs, and so does [https://github.com/kaz-yos/eval-in-repl eval-in-repl] (in MELPA). With the latter, just use '''C-RET'''.<br />
<br />
=== See also ===<br />
<br />
* [https://github.com/sriramkswamy/ryo-emacs/blob/master/config/sk-python.el sk's utilities for datascience]: several helper functions, similar to <code>ess-describe-object-at-point</code>, to get the shape, type and sum of the symbol at point. It works very well for my needs and doesn't need any extra package - just the built-in python-mode. There are also keybindings setup to send various chunks of code.<br />
<br />
== Other tools ==<br />
<br />
=== Virtual environments ===<br />
<br />
Some tools allow to apply the changes of virtual environment activation inside emacs. They make '''M-x compile''' aware of the environment, etc.<br />
<br />
* [https://github.com/porterjamesj/virtualenvwrapper.el virtualenvwrapper] emulates much of the functionnality of '''virtualenvwrapper''', integrates well with '''M-x shell''' or '''eshell''', is aware of hooks, has an automatic activation by project and integrates in the mode line.<br />
<br />
* [https://github.com/jorgenschaefer/pyvenv pyvenv] sets the python path, uses virtualwrapper's hooks, ...<br />
<br />
=== Python versions (pyenv) ===<br />
<br />
We can change python versions with [https://github.com/proofit404/pyenv-mode pyenv-mode] (in melpa) and automatically when there is a .python-version file with [https://github.com/ssbb/pyenv-mode-auto pyenv-mode-auto].<br />
<br />
Once it's installed, we just have to switch with '''M-x pyenv-mode-set'''.<br />
<br />
=== Pymacs ===<br />
<br />
'''{{ModeLink|Pymacs}}''' is an Emacs extension that enables the use of Python alongside with Emacs Lisp.<br />
<br />
[http://pymacs.progiciels-bpi.ca/index.html Pymacs homepage]<br />
<br />
=== include import statements or remove unused ===<br />
<br />
[[Ropemacs]] (see above) is a plugin for performing python refactorings in emacs. It uses rope library and pymacs. It has '''rope-auto-import''', so if you write <br />
<br />
rmtree<br />
<br />
and then execute {{Command|rope-auto-import}}, <br />
<br />
from shutil import rmtree<br />
<br />
is inserted at the top of the file.<br />
<br />
Unfortunately Ropemacs can not do non-relative imports, it can only create imports of the "from X import Y" variety (if you type ''shutil.rmtree'' it doesn't write ''import shutil'').<br />
<br />
[https://github.com/Wilfred/pyimport pyimport] can add import statements or remove the unused ones (with pyflakes).<br />
<br />
[http://elpy.readthedocs.io/en/latest/ide.html?highlight=django#refactoring Elpy] too can import missing ones.<br />
<br />
See also [https://gitlab.com/emacs-stuff/python-import-add/ a snippet] to add many imports at once.<br />
<br />
=== Sort import statements ===<br />
<br />
See the '''py-isort''' [[Melpa]] package to automatically sort import statements.<br />
<br />
=== pip-requirements mode ===<br />
<br />
[http://melpa.org/#/pip-requirements pip-requirements] (in MELPA) is a major mode for editing pip requirements files, with the following features:<br />
* syntax highlighting<br />
* Auto completion of package names from PyPI<br />
* togglable comments<br />
<br />
=== pip utilities ===<br />
<br />
[https://github.com/brotzeitmacher/pippel pippel] (in melpa) provides a similar package menu as "package-list-packages", to list, install, upgrade, remove etc pip packages.<br />
<br />
[https://gitlab.com/emacs-stuff/pip-utils pip-utils] (not in melpa) provides some functions with completion of packages and of the requirements files of the project:<br />
<br />
* choose one requirements file of the project if many and install its packages,<br />
* chooses the right virtual env,<br />
* install a new package and add it into a requirements file (with interactive choice, needed when there is a "dev-requirements" for instance),<br />
* check the current package version (with pip freeze),<br />
* open the package page on pypi.<br />
<br />
=== Code coverage with Python 3 ===<br />
<br />
There's a tool to highlight in real time the lines that are (not) covered by your unit tests. It's called [https://github.com/mattharrison/pycoverage.el pycoverage.el] and it is in [[melpa]].<br />
<br />
== Libraries ==<br />
<br />
Let's put them on [[Python libraries]]. Hints to write Emacs packages for Python projects.<br />
<br />
== See also ==<br />
<br />
You'll be certainly interested in the following packages (that you will find on [[ELPA]] or MELPA):<br />
<br />
=== '''Magit''', a git interface === <br />
<br />
Emacs + git is magic : see [[magit]]<br />
<br />
=== Code navigation: jump to function definitions ===<br />
<br />
Get started with [[imenu]] and '''helm-imenu''' (see [[helm]]).<br />
<br />
Then for cross-project code navigation see xcscope that answers questions like "show all methods that call this one".<br />
<br />
See also '''grep''', '''rgrep''', '''occur''', [https://github.com/ShingoFukuyama/helm-swoop helm-swoop] (interactive grep of the current buffer) and enhanced grep tools like [https://github.com/Wilfred/ag.el ag] and its related helm-ag.<br />
<br />
=== Code navigation: move by indentation levels ===<br />
<br />
See [https://gitlab.com/emacs-stuff/indent-tools indent-tools] (in MELPA) that allows to move and fire actions by levels of indentation, for code source like Python or Yaml. For example: go to the next line that has the same indentation level, comment/kill/fold/… the current indentation level, the current paragraph, etc.<br />
<br />
<br />
[[File:indent-tools.gif]]<br />
<br />
=== '''Yasnippet''', a template system ===<br />
<br />
[[yasnippet]]<br />
<br />
=== '''helm-pydoc''' to browse the documentation of installed packages and import one ===<br />
<br />
=== '''pungi''' to integrate jedi, virtualenv and buildout ===<br />
<br />
=== How to do code folding ===<br />
<br />
See [[folding]]<br />
<br />
=== other '''ELPA packages''' === <br />
<br />
If you're running Emacs with package support (usually Emacs 24 and later), check out what is available in [[ELPA]]:<br />
; {{Command | list-packages}} : and see flymake-pyhon-pyflakes, flymake-shell, abl-mode (a python TDD minor-mode), nose (easy python test-running in emacs), visual-regexp / visual-regexp-steroids, python-magic and more.<br />
<br />
[[Category:Programming languages]]<br />
[[Category:Programming]]<br />
[[Category:Python]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50748Main Page2017-08-15T03:00:23Z<p>Holocronweaver: </p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=MediaWiki:Requestaccount-notes&diff=50747MediaWiki:Requestaccount-notes2017-08-15T02:54:36Z<p>Holocronweaver: </p>
<hr />
<div>Please list your top three favorite Emacs features (or your top three reasons for wanting to use Emacs if you are new):</div>Holocronweaverhttps://wikemacs.org/index.php?title=MediaWiki:Requestaccount-notes&diff=50746MediaWiki:Requestaccount-notes2017-08-15T02:51:43Z<p>Holocronweaver: </p>
<hr />
<div>'''Please list your top three favorite Emacs features:'''</div>Holocronweaverhttps://wikemacs.org/index.php?title=MediaWiki:Requestaccount-ext-text&diff=50745MediaWiki:Requestaccount-ext-text2017-08-15T02:51:25Z<p>Holocronweaver: Created page with "The following information is kept private and will only be used to verify you are not a bot."</p>
<hr />
<div>The following information is kept private and will only be used to verify you are not a bot.</div>Holocronweaverhttps://wikemacs.org/index.php?title=MediaWiki:Requestaccount-notes&diff=50744MediaWiki:Requestaccount-notes2017-08-15T02:49:04Z<p>Holocronweaver: Created page with "Please include at least one interesting thing about you (so we know you're not a bot!):"</p>
<hr />
<div>Please include at least one interesting thing about you (so we know you're not a bot!):</div>Holocronweaverhttps://wikemacs.org/index.php?title=Talk:Main_Page&diff=50743Talk:Main Page2017-08-05T07:04:56Z<p>Holocronweaver: Holocronweaver moved page Talk:IntiUT™1∞(844-745-8575) Quickbooks support phone number ™1∞(844-745-8575) Quickbooks customer to Talk:Main Page without leaving a redirect: revert spam</p>
<hr />
<div>== IMPORTANT: Offline discussion ==<br />
<br />
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)<br />
<br />
== IMPORTANT: Content Quality guidelines ==<br />
I think before flame wars and fights among members, we should form<br />
proper/strict guide lines for each aspect of the site. [http://depuypinnaclelawsuit.webnode.com/ DePuy Pinnacle Lawsuit] Wikipedia has very strict<br />
rules about that., even their bots can tell the content quality of a<br />
page. we can create articles in "WikEmacs" Namespace. [[User:Kindahero|Kindahero]] 23:57, 1 April 2012 (EEST)<br />
<br />
:Wikipedia has lots of rules today, but it started with very few rules and they invented the rules as they became necessary. It's impossible to predict what problems will be encountered. I'd suggest that rules only be made when it becomes clear that one is necessary. [[User:Ciaran|Ciaran]] 15:24, 29 January 2013 (EET)<br />
<br />
== Structure ==<br />
I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?<br />
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)<br />
<br />
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)<br />
<br />
== Markup Conventions== <br />
<br />
=== Wikipedia linking convention ===<br />
<br />
Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)<br />
<br />
=== EmacsWiki linking convention ===<br />
<br />
Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)<br />
<br />
== Describing Modes and Packages ==<br />
<br />
=== Naming Conventions ===<br />
<br />
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)<br />
<br />
:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::::Not ship, but a haskell-mode definitely exists and is in use...--[[Special:Contributions/84.192.109.230|84.192.109.230]] 18:33, 11 January 2013 (EET)<br />
<br />
== Template for mode-with-github-source pages? ==<br />
<br />
Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)<br />
<br />
== Issues == <br />
* The "Editing Help" link goes to a virgin page, not the full help page.<br />
* Add [http://meta.wikimedia.org/wiki/Help:Footnotes Mediawiki Cite extension] to enable footnotes.<br />
* Add [http://meta.wikimedia.org/wiki/Category#Visualizing_category_tree Category Tree extension] to explore various categories like [[:Category:Programming languages]].<br />
<br />
== Syntax highlighting ==<br />
<br />
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)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
::: 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)<br />
<br />
::::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. <br />
::::<pre>This is just an ordinary PRE element.</pre><br />
::::<syntaxhighlight lang="html4strict">This is a PRE element generated by the syntax highlighting plugin.</syntaxhighlight><br />
::::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)<br />
::::: I only find the second one small not the both. I started with 'firefox -safe-mode' still the same. It seems its general problem with Geshi see http://stackoverflow.com/questions/5354968/changing-the-font-size-of-code-formatted-by-syntaxhighlight-geshi-in-mediawiki [[User:Kindahero|Kindahero]] 20:25, 1 April 2012 (EEST)<br />
<br />
==fails to create thumbnails==<br />
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)<br />
: found this link, http://www.mediawiki.org/wiki/Manual:Configuration_settings#Thumbnail_settings [[User:Kindahero|Kindahero]] 16:24, 31 March 2012 (EEST)<br />
:: 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)<br />
<br />
:I see that on <nowiki>[[File:Screenshot-dictem-buffer.jpg]]</nowiki>, the main image is not displayed. The "Full resolution" link shows a valid image. By the way, this type of question might be appropriate for [https://groups.google.com/forum/?fromgroups#!forum/wikemacs Google Groups:WikEmacs]. [[User:Xophist|Xophist]] 21:31, 1 April 2012 (EEST)<br />
<br />
== needed plugins ==<br />
<br />
* cite.php is needed to show references using <nowiki><ref> </ref></nowiki> for example http://wikemacs.org/wiki/Battery#How_to_show_battery_status_only_on_laptop.3F has ref, but not working.?<br />
<br />
:I had this problem when getting Cite_web set up on en.swpat.org. If I look into how I got it working, could it be fixed here too? [[User:Ciaran|Ciaran]] 15:31, 29 January 2013 (EET)<br />
<br />
<br />
== WikEmacs staying open? Great! ==<br />
<br />
Glad to hear it's not closing. Anything we (new contributors) should know? Is anything changing? [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 09:51, 20 April 2013 (EDT)<br />
<br />
: Hello, I am the new caretaker of WikEmacs. No major changes have been made. This will continue to be a site by and for the users, so I welcome all input for suggested changes. As the site expands and users return, we will likely need to revisit the control structure and possibly modify the site rules. For now I would like to focus on growing the wiki. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 15:09, 22 April 2013 (EDT)<br />
<br />
:: Take a look at this: [http://www.emacswiki.org/emacs/BackwardKillLine BackwardKillLine on emacswiki]. If just reading this article does not inspire you to to keep WikEmacs open, nothing will I'm afraid. --[[User:Holocronweaver|Holocronweaver]] 22:30, 22 February 2013 (EET)<br />
<br />
== Keeping the licence situation clear and clean ==<br />
<br />
Just noting the current situation...<br />
<br />
* emacswiki.org is published under multiple licences, including GPLv2, GFDL (no version specified), CC-sa, and their own [http://www.emacswiki.org/OLD simple permissive licence].<br />
* The GNU Emacs manual is published under GFDLv1.3+<br />
* Existing WikEmacs texts are under GFDLv1.3+<br />
<br />
For emacswiki.org, we could either ask them to specify their version(s) of GFDL, or we could use their text under their simple permissive licence. If we do the latter, we could include a mention of their copyright notice either in the default copyright notice at the bottom of all WikEmacs pages, or we could create a template "''This page includes text from emacswiki.org, used under [http://www.emacswiki.org/OLD this licence]''".<br />
<br />
For the GNU Emacs manual, if we're going to continue using GFDLv1.3+, then we don't have to do anything. But if we want to switch to the dual-licence model used by Wikipedia (and accepted by Stallman), then whenever we copy text from the manual, we'd have to put a template on those pages to say that those pages are only available under GFDLv1.3+ (and not CC-sa).<br />
<br />
For text by WikEmacs contributors, we could continue to license it under GFDLv1.3+, or we could say that from now on, contributions are under the Wikipedia-style dual-licence (GFDLv1.3+ and CC-sa). This wouldn't change much but it would give us more options in the future if we do encounter problems.<br />
<br />
I'll have to think for a while before having any recommendations, and there's currently nothing messy or problematic, but just wanted to note the situation early on in case anyone wants to make suggestions. I have experience with licensing issues. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:02, 23 April 2013 (EDT)<br />
<br />
: I have spent some time thinking on this, and your suggestion of asking emacswiki.org to clarify their version of GFDL appears to be simplest. That way WikEmacs could maintain its current GFDLv1.3+ license and no ugly licensing notices would be necessary when porting content from emacswiki.org, assuming thes choose GFDLv1.3+. In the event they choose a different version of GFDL, is it possible to port old versions of the license to new versions so we could use the material under GFDL1.3+? --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 13:30, 3 May 2013 (EDT)<br />
<br />
::Ok, I've thought through the scenarios now. The current Wikemacs licence notice is fine: if wikemacs contains original content plus emacswiki content plus GNU manual content plus Wikipedia content, it will always be true that the recipient can distribute under GFDL v1.3 or any later version. (emacswiki doesn't textually say "v1.3+" but all their pages are also under a [http://www.emacswiki.org/OLD do what you want, just preserve our copyright notice] licence, so GFDL version ambiguities can be ignored.) So nothing has to be changed in the footer.<br />
<br />
::The two other issues are the copyright details, and the licence of original contributions.<br />
<br />
::Copyright details. If we include material from the manual/wikipedia/emacswiki, then we have to mention this somewhere (otherwise we'd be claiming to own stuff we copied from them). At a minimum, we have to put a general statement in [[WikEmacs:Copyrights]] to say "''Some pages incorporate text from XYZ, received under <copy of their licence notice>''".<br />
<br />
::Legally, that's all that's necessary. But, by lacking precision it leads to certain inconveniences. For example, if someone wants to copy an article from here that contains just original content, they should be able to include just a single line "''copyright 2013 Wikemacs''", but if there's no way to see that it's original content then that person will have to include all the "''this may contain...''" statements from [[WikEmacs:Copyrights]]. Or if there's a problem later (such as someone adding non-free content to emacswiki, and us copying it over), we're left with a mess not knowing what pages have to be checked/reverted.<br />
<br />
::(This reminds me that the copyright situation of my own wiki is not a shining example, but that's less problematic since all material is original content.)<br />
<br />
::So, for keeping track of copyrights, nothing is ''required'' and complexity just makes people less likely to do it, so it's just a matter of picking the low hanging fruit. I see four possibilities:<br />
::# Mention "''from XYZ''" in the edit summary. Drawback: if someone forgot to do this, there's no way to go back later and put it into the edit summary, and, the only way to search all edit summaries is by going to each page... tedious.<br />
::# Mention it on the page. This is what wikipedia does. Make a template so that editors can add <nowiki>{{</nowiki>copyright manual}} to the bottom of the page or in the "References" section to add one sentence "''This page incorporates bla bla see [[WikEmacs:Copyrights]]''".<br />
::# Same, but put it at the top of the Talk: page.<br />
::# Make a page for listing which pages contain substantial amounts of material from what sources.<br />
::The last two look nice and clean but that's also a drawback since if reader-contributors don't see how copyright info is noted, they won't realise that they should also make a note when they add third-party content to a page. The second solution adds a bit of mess to the page, but it works well with the wiki model of learn-by-copying.<br />
<br />
::If in doubt, I'd go with the second option. (Copying Wikipedia is usually a safe move.) We can always change at a later stage.<br />
<br />
::The last thing is the licence of new contributions (i.e. what should the notice under the edit box say "''all contributions to WikEmacs are considered to be released under...''"). My usual reflex is to use GNU whatever, but Stallman did give Wikipedia the green light to move to a dual GFDL + CC-by-sa for original contributions. I can't remember all the problems that motivated Wikipedia to migrate, but I think there were some issues like GFDL's requirement to include a copy of the licence when distributing covered works (so when you print a 2-page article, you have to add the 10 pages of the licence). Copying Wikipedia's approach probably has some practical advantages for people re-using Wikemacs material, and it allows people to copy material from Wikemacs into Wikipedia (while still being able to copy wikemacs material into the GNU manuals etc.). So for new contributions, a plain GFDLv1.3+ is fine, but the Wikipedia model is probably better. This wouldn't change the footer - GFDL would still be our primary licence since some pages would combine original content (GFDL+CC-by-sa) with content from the GNU manual (GFDL only) and the combination could only be distributed under GFDL, not CC-by-sa.<br />
<br />
::It would also be a good idea for the notice under the edit box to tell people "''If you incorporate material from the GNU manual, please include <nowiki>{{</nowiki>copyright manual}} at the end of the page''", and similar for emacswiki and Wikipedia.<br />
<br />
::Hope that helps. I'll be back at the end of June. None of this is urgent anyway. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:27, 3 June 2013 (EDT)<br />
<br />
== Which emacswiki.org topics to work on? ==<br />
<br />
So, for each of the useful pages on emacswiki.org, we should make our own pages for those topics and incorporate the knowledge that's in the emacswiki.org pages, but how do we make a list of the useful emacswiki.org pages?<br />
<br />
Does the site have any equivalents to MediaWiki's pages:<br />
<br />
* [[Special:LongPages]]<br />
* [[Special:MostLinkedPages]]<br />
* [[Special:MostRevisions]]<br />
<br />
? (But IMO we should take a decision on the licence before doing a lot of work.) [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 12:27, 24 April 2013 (EDT)<br />
<br />
:If not, I wonder if search engines could help us approximate the "value" of each page?<br />
<br />
:* https://www.google.com/search?q=site%3Aemacswiki.org<br />
<br />
:Hmm. I'd take that as a no. Looks like a random selection. Any other ideas?<br />
<br />
:Finding the pages with the most revisions shouldn't be too hard. Just involves a script downloading the history of [http://www.emacswiki.org/emacs/?action=printable-index each page] and sorting by length. That might give an indication of the good pages.<br />
<br />
:The [http://www.alexa.com/siteinfo/emacswiki.org info on alexa.com] isn't too solid, but gives some hints about what people look for. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 11:19, 3 June 2013 (EDT)<br />
::I will look into this. In the mean time, I would edit articles whenever you cannot you find the information you want on the wiki. This is how I edit wikis in general. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 22:07, 26 November 2013 (EST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=Talk:Main_Page&diff=50742Talk:Main Page2017-08-05T07:03:39Z<p>Holocronweaver: revert spam</p>
<hr />
<div>== IMPORTANT: Offline discussion ==<br />
<br />
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)<br />
<br />
== IMPORTANT: Content Quality guidelines ==<br />
I think before flame wars and fights among members, we should form<br />
proper/strict guide lines for each aspect of the site. [http://depuypinnaclelawsuit.webnode.com/ DePuy Pinnacle Lawsuit] Wikipedia has very strict<br />
rules about that., even their bots can tell the content quality of a<br />
page. we can create articles in "WikEmacs" Namespace. [[User:Kindahero|Kindahero]] 23:57, 1 April 2012 (EEST)<br />
<br />
:Wikipedia has lots of rules today, but it started with very few rules and they invented the rules as they became necessary. It's impossible to predict what problems will be encountered. I'd suggest that rules only be made when it becomes clear that one is necessary. [[User:Ciaran|Ciaran]] 15:24, 29 January 2013 (EET)<br />
<br />
== Structure ==<br />
I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?<br />
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)<br />
<br />
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)<br />
<br />
== Markup Conventions== <br />
<br />
=== Wikipedia linking convention ===<br />
<br />
Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)<br />
<br />
=== EmacsWiki linking convention ===<br />
<br />
Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)<br />
<br />
== Describing Modes and Packages ==<br />
<br />
=== Naming Conventions ===<br />
<br />
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)<br />
<br />
:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::::Not ship, but a haskell-mode definitely exists and is in use...--[[Special:Contributions/84.192.109.230|84.192.109.230]] 18:33, 11 January 2013 (EET)<br />
<br />
== Template for mode-with-github-source pages? ==<br />
<br />
Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)<br />
<br />
== Issues == <br />
* The "Editing Help" link goes to a virgin page, not the full help page.<br />
* Add [http://meta.wikimedia.org/wiki/Help:Footnotes Mediawiki Cite extension] to enable footnotes.<br />
* Add [http://meta.wikimedia.org/wiki/Category#Visualizing_category_tree Category Tree extension] to explore various categories like [[:Category:Programming languages]].<br />
<br />
== Syntax highlighting ==<br />
<br />
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)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
::: 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)<br />
<br />
::::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. <br />
::::<pre>This is just an ordinary PRE element.</pre><br />
::::<syntaxhighlight lang="html4strict">This is a PRE element generated by the syntax highlighting plugin.</syntaxhighlight><br />
::::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)<br />
::::: I only find the second one small not the both. I started with 'firefox -safe-mode' still the same. It seems its general problem with Geshi see http://stackoverflow.com/questions/5354968/changing-the-font-size-of-code-formatted-by-syntaxhighlight-geshi-in-mediawiki [[User:Kindahero|Kindahero]] 20:25, 1 April 2012 (EEST)<br />
<br />
==fails to create thumbnails==<br />
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)<br />
: found this link, http://www.mediawiki.org/wiki/Manual:Configuration_settings#Thumbnail_settings [[User:Kindahero|Kindahero]] 16:24, 31 March 2012 (EEST)<br />
:: 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)<br />
<br />
:I see that on <nowiki>[[File:Screenshot-dictem-buffer.jpg]]</nowiki>, the main image is not displayed. The "Full resolution" link shows a valid image. By the way, this type of question might be appropriate for [https://groups.google.com/forum/?fromgroups#!forum/wikemacs Google Groups:WikEmacs]. [[User:Xophist|Xophist]] 21:31, 1 April 2012 (EEST)<br />
<br />
== needed plugins ==<br />
<br />
* cite.php is needed to show references using <nowiki><ref> </ref></nowiki> for example http://wikemacs.org/wiki/Battery#How_to_show_battery_status_only_on_laptop.3F has ref, but not working.?<br />
<br />
:I had this problem when getting Cite_web set up on en.swpat.org. If I look into how I got it working, could it be fixed here too? [[User:Ciaran|Ciaran]] 15:31, 29 January 2013 (EET)<br />
<br />
<br />
== WikEmacs staying open? Great! ==<br />
<br />
Glad to hear it's not closing. Anything we (new contributors) should know? Is anything changing? [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 09:51, 20 April 2013 (EDT)<br />
<br />
: Hello, I am the new caretaker of WikEmacs. No major changes have been made. This will continue to be a site by and for the users, so I welcome all input for suggested changes. As the site expands and users return, we will likely need to revisit the control structure and possibly modify the site rules. For now I would like to focus on growing the wiki. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 15:09, 22 April 2013 (EDT)<br />
<br />
:: Take a look at this: [http://www.emacswiki.org/emacs/BackwardKillLine BackwardKillLine on emacswiki]. If just reading this article does not inspire you to to keep WikEmacs open, nothing will I'm afraid. --[[User:Holocronweaver|Holocronweaver]] 22:30, 22 February 2013 (EET)<br />
<br />
== Keeping the licence situation clear and clean ==<br />
<br />
Just noting the current situation...<br />
<br />
* emacswiki.org is published under multiple licences, including GPLv2, GFDL (no version specified), CC-sa, and their own [http://www.emacswiki.org/OLD simple permissive licence].<br />
* The GNU Emacs manual is published under GFDLv1.3+<br />
* Existing WikEmacs texts are under GFDLv1.3+<br />
<br />
For emacswiki.org, we could either ask them to specify their version(s) of GFDL, or we could use their text under their simple permissive licence. If we do the latter, we could include a mention of their copyright notice either in the default copyright notice at the bottom of all WikEmacs pages, or we could create a template "''This page includes text from emacswiki.org, used under [http://www.emacswiki.org/OLD this licence]''".<br />
<br />
For the GNU Emacs manual, if we're going to continue using GFDLv1.3+, then we don't have to do anything. But if we want to switch to the dual-licence model used by Wikipedia (and accepted by Stallman), then whenever we copy text from the manual, we'd have to put a template on those pages to say that those pages are only available under GFDLv1.3+ (and not CC-sa).<br />
<br />
For text by WikEmacs contributors, we could continue to license it under GFDLv1.3+, or we could say that from now on, contributions are under the Wikipedia-style dual-licence (GFDLv1.3+ and CC-sa). This wouldn't change much but it would give us more options in the future if we do encounter problems.<br />
<br />
I'll have to think for a while before having any recommendations, and there's currently nothing messy or problematic, but just wanted to note the situation early on in case anyone wants to make suggestions. I have experience with licensing issues. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:02, 23 April 2013 (EDT)<br />
<br />
: I have spent some time thinking on this, and your suggestion of asking emacswiki.org to clarify their version of GFDL appears to be simplest. That way WikEmacs could maintain its current GFDLv1.3+ license and no ugly licensing notices would be necessary when porting content from emacswiki.org, assuming thes choose GFDLv1.3+. In the event they choose a different version of GFDL, is it possible to port old versions of the license to new versions so we could use the material under GFDL1.3+? --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 13:30, 3 May 2013 (EDT)<br />
<br />
::Ok, I've thought through the scenarios now. The current Wikemacs licence notice is fine: if wikemacs contains original content plus emacswiki content plus GNU manual content plus Wikipedia content, it will always be true that the recipient can distribute under GFDL v1.3 or any later version. (emacswiki doesn't textually say "v1.3+" but all their pages are also under a [http://www.emacswiki.org/OLD do what you want, just preserve our copyright notice] licence, so GFDL version ambiguities can be ignored.) So nothing has to be changed in the footer.<br />
<br />
::The two other issues are the copyright details, and the licence of original contributions.<br />
<br />
::Copyright details. If we include material from the manual/wikipedia/emacswiki, then we have to mention this somewhere (otherwise we'd be claiming to own stuff we copied from them). At a minimum, we have to put a general statement in [[WikEmacs:Copyrights]] to say "''Some pages incorporate text from XYZ, received under <copy of their licence notice>''".<br />
<br />
::Legally, that's all that's necessary. But, by lacking precision it leads to certain inconveniences. For example, if someone wants to copy an article from here that contains just original content, they should be able to include just a single line "''copyright 2013 Wikemacs''", but if there's no way to see that it's original content then that person will have to include all the "''this may contain...''" statements from [[WikEmacs:Copyrights]]. Or if there's a problem later (such as someone adding non-free content to emacswiki, and us copying it over), we're left with a mess not knowing what pages have to be checked/reverted.<br />
<br />
::(This reminds me that the copyright situation of my own wiki is not a shining example, but that's less problematic since all material is original content.)<br />
<br />
::So, for keeping track of copyrights, nothing is ''required'' and complexity just makes people less likely to do it, so it's just a matter of picking the low hanging fruit. I see four possibilities:<br />
::# Mention "''from XYZ''" in the edit summary. Drawback: if someone forgot to do this, there's no way to go back later and put it into the edit summary, and, the only way to search all edit summaries is by going to each page... tedious.<br />
::# Mention it on the page. This is what wikipedia does. Make a template so that editors can add <nowiki>{{</nowiki>copyright manual}} to the bottom of the page or in the "References" section to add one sentence "''This page incorporates bla bla see [[WikEmacs:Copyrights]]''".<br />
::# Same, but put it at the top of the Talk: page.<br />
::# Make a page for listing which pages contain substantial amounts of material from what sources.<br />
::The last two look nice and clean but that's also a drawback since if reader-contributors don't see how copyright info is noted, they won't realise that they should also make a note when they add third-party content to a page. The second solution adds a bit of mess to the page, but it works well with the wiki model of learn-by-copying.<br />
<br />
::If in doubt, I'd go with the second option. (Copying Wikipedia is usually a safe move.) We can always change at a later stage.<br />
<br />
::The last thing is the licence of new contributions (i.e. what should the notice under the edit box say "''all contributions to WikEmacs are considered to be released under...''"). My usual reflex is to use GNU whatever, but Stallman did give Wikipedia the green light to move to a dual GFDL + CC-by-sa for original contributions. I can't remember all the problems that motivated Wikipedia to migrate, but I think there were some issues like GFDL's requirement to include a copy of the licence when distributing covered works (so when you print a 2-page article, you have to add the 10 pages of the licence). Copying Wikipedia's approach probably has some practical advantages for people re-using Wikemacs material, and it allows people to copy material from Wikemacs into Wikipedia (while still being able to copy wikemacs material into the GNU manuals etc.). So for new contributions, a plain GFDLv1.3+ is fine, but the Wikipedia model is probably better. This wouldn't change the footer - GFDL would still be our primary licence since some pages would combine original content (GFDL+CC-by-sa) with content from the GNU manual (GFDL only) and the combination could only be distributed under GFDL, not CC-by-sa.<br />
<br />
::It would also be a good idea for the notice under the edit box to tell people "''If you incorporate material from the GNU manual, please include <nowiki>{{</nowiki>copyright manual}} at the end of the page''", and similar for emacswiki and Wikipedia.<br />
<br />
::Hope that helps. I'll be back at the end of June. None of this is urgent anyway. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:27, 3 June 2013 (EDT)<br />
<br />
== Which emacswiki.org topics to work on? ==<br />
<br />
So, for each of the useful pages on emacswiki.org, we should make our own pages for those topics and incorporate the knowledge that's in the emacswiki.org pages, but how do we make a list of the useful emacswiki.org pages?<br />
<br />
Does the site have any equivalents to MediaWiki's pages:<br />
<br />
* [[Special:LongPages]]<br />
* [[Special:MostLinkedPages]]<br />
* [[Special:MostRevisions]]<br />
<br />
? (But IMO we should take a decision on the licence before doing a lot of work.) [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 12:27, 24 April 2013 (EDT)<br />
<br />
:If not, I wonder if search engines could help us approximate the "value" of each page?<br />
<br />
:* https://www.google.com/search?q=site%3Aemacswiki.org<br />
<br />
:Hmm. I'd take that as a no. Looks like a random selection. Any other ideas?<br />
<br />
:Finding the pages with the most revisions shouldn't be too hard. Just involves a script downloading the history of [http://www.emacswiki.org/emacs/?action=printable-index each page] and sorting by length. That might give an indication of the good pages.<br />
<br />
:The [http://www.alexa.com/siteinfo/emacswiki.org info on alexa.com] isn't too solid, but gives some hints about what people look for. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 11:19, 3 June 2013 (EDT)<br />
::I will look into this. In the mean time, I would edit articles whenever you cannot you find the information you want on the wiki. This is how I edit wikis in general. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 22:07, 26 November 2013 (EST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50741Main Page2017-08-05T06:58:13Z<p>Holocronweaver: </p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
'''NOTICE 2017-08-04''': Due to recent massive spam attacks, user registration is temporarily suspended. This should be lifted shortly.<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50740Main Page2017-07-28T17:26:45Z<p>Holocronweaver: Reverted edits by Support (talk) to last revision by Holocronweaver</p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50658Main Page2017-07-28T17:08:16Z<p>Holocronweaver: Holocronweaver moved page User talk:Google support number 1855+478+3289 google support phone number to Main Page without leaving a redirect: revert spam</p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=50653Main Page2017-07-28T17:06:35Z<p>Holocronweaver: revert page</p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** Add content. Please adopt the following approach - ''I found this on the web 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''. You can start by documenting Emacs' support of your favorite programming language. <br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
** Follow the [http://wikemacs.org/api.php?hidebots=1&days=7&limit=50&action=feedrecentchanges&feedformat=atom RSS feed] to watch edits, new users and help fighting vandalism (fortunately quite low).<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[Financial_Support|Financial Supporter]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=47737Main Page2017-02-08T21:15:18Z<p>Holocronweaver: Minor capitalization typo</p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** 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.''<br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 25|Emacs-25.1]] released on September 17th, 2016. The precedent is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Talk:Main_Page&diff=47586Talk:Main Page2016-08-17T20:58:21Z<p>Holocronweaver: roll back before spam</p>
<hr />
<div>== IMPORTANT: Offline discussion ==<br />
<br />
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)<br />
<br />
== IMPORTANT: Content Quality guidelines ==<br />
I think before flame wars and fights among members, we should form<br />
proper/strict guide lines for each aspect of the site. [http://depuypinnaclelawsuit.webnode.com/ DePuy Pinnacle Lawsuit] Wikipedia has very strict<br />
rules about that., even their bots can tell the content quality of a<br />
page. we can create articles in "WikEmacs" Namespace. [[User:Kindahero|Kindahero]] 23:57, 1 April 2012 (EEST)<br />
<br />
:Wikipedia has lots of rules today, but it started with very few rules and they invented the rules as they became necessary. It's impossible to predict what problems will be encountered. I'd suggest that rules only be made when it becomes clear that one is necessary. [[User:Ciaran|Ciaran]] 15:24, 29 January 2013 (EET)<br />
<br />
== Structure ==<br />
I would like to structure the Main Page in boxes like here [http://www.webos-internals.org] the Featured Article/Project. Any objections?<br />
And maybe [[User:Bozhidar]] should write some lines about the relation to the "old" EmacsWiki?--[[User:Kenda|Kenda]] 19:58, 24 March 2012 (EET)<br />
<br />
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)<br />
<br />
== Markup Conventions== <br />
<br />
=== Wikipedia linking convention ===<br />
<br />
Could/should we have a convention for formatting and placement of wikipedia links on pages? [[User:PhilHudson|PhilHudson]] 22:37, 24 March 2012 (EET)<br />
<br />
=== EmacsWiki linking convention ===<br />
<br />
Similar question to Wikipedia wrt EmacsWiki [[User:PhilHudson|PhilHudson]] 23:06, 24 March 2012 (EET)<br />
<br />
== Describing Modes and Packages ==<br />
<br />
=== Naming Conventions ===<br />
<br />
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)<br />
<br />
:Agreed, let's use the "friendly" name of a package. I'd say "Org", "Gnus", "YASnippet", etc. [[User:GregLucas|GregLucas]]<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
:::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)<br />
<br />
::::Not ship, but a haskell-mode definitely exists and is in use...--[[Special:Contributions/84.192.109.230|84.192.109.230]] 18:33, 11 January 2013 (EET)<br />
<br />
== Template for mode-with-github-source pages? ==<br />
<br />
Can Wikimedia do page templates? I'm sure the answer is yes. [[User:PhilHudson|PhilHudson]] 23:07, 24 March 2012 (EET)<br />
<br />
== Issues == <br />
* The "Editing Help" link goes to a virgin page, not the full help page.<br />
* Add [http://meta.wikimedia.org/wiki/Help:Footnotes Mediawiki Cite extension] to enable footnotes.<br />
* Add [http://meta.wikimedia.org/wiki/Category#Visualizing_category_tree Category Tree extension] to explore various categories like [[:Category:Programming languages]].<br />
<br />
== Syntax highlighting ==<br />
<br />
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)<br />
<br />
: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)<br />
<br />
::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)<br />
<br />
::: 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)<br />
<br />
::::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. <br />
::::<pre>This is just an ordinary PRE element.</pre><br />
::::<syntaxhighlight lang="html4strict">This is a PRE element generated by the syntax highlighting plugin.</syntaxhighlight><br />
::::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)<br />
::::: I only find the second one small not the both. I started with 'firefox -safe-mode' still the same. It seems its general problem with Geshi see http://stackoverflow.com/questions/5354968/changing-the-font-size-of-code-formatted-by-syntaxhighlight-geshi-in-mediawiki [[User:Kindahero|Kindahero]] 20:25, 1 April 2012 (EEST)<br />
<br />
==fails to create thumbnails==<br />
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)<br />
: found this link, http://www.mediawiki.org/wiki/Manual:Configuration_settings#Thumbnail_settings [[User:Kindahero|Kindahero]] 16:24, 31 March 2012 (EEST)<br />
:: 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)<br />
<br />
:I see that on <nowiki>[[File:Screenshot-dictem-buffer.jpg]]</nowiki>, the main image is not displayed. The "Full resolution" link shows a valid image. By the way, this type of question might be appropriate for [https://groups.google.com/forum/?fromgroups#!forum/wikemacs Google Groups:WikEmacs]. [[User:Xophist|Xophist]] 21:31, 1 April 2012 (EEST)<br />
<br />
== needed plugins ==<br />
<br />
* cite.php is needed to show references using <nowiki><ref> </ref></nowiki> for example http://wikemacs.org/wiki/Battery#How_to_show_battery_status_only_on_laptop.3F has ref, but not working.?<br />
<br />
:I had this problem when getting Cite_web set up on en.swpat.org. If I look into how I got it working, could it be fixed here too? [[User:Ciaran|Ciaran]] 15:31, 29 January 2013 (EET)<br />
<br />
<br />
== WikEmacs staying open? Great! ==<br />
<br />
Glad to hear it's not closing. Anything we (new contributors) should know? Is anything changing? [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 09:51, 20 April 2013 (EDT)<br />
<br />
: Hello, I am the new caretaker of WikEmacs. No major changes have been made. This will continue to be a site by and for the users, so I welcome all input for suggested changes. As the site expands and users return, we will likely need to revisit the control structure and possibly modify the site rules. For now I would like to focus on growing the wiki. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 15:09, 22 April 2013 (EDT)<br />
<br />
:: Take a look at this: [http://www.emacswiki.org/emacs/BackwardKillLine BackwardKillLine on emacswiki]. If just reading this article does not inspire you to to keep WikEmacs open, nothing will I'm afraid. --[[User:Holocronweaver|Holocronweaver]] 22:30, 22 February 2013 (EET)<br />
<br />
== Keeping the licence situation clear and clean ==<br />
<br />
Just noting the current situation...<br />
<br />
* emacswiki.org is published under multiple licences, including GPLv2, GFDL (no version specified), CC-sa, and their own [http://www.emacswiki.org/OLD simple permissive licence].<br />
* The GNU Emacs manual is published under GFDLv1.3+<br />
* Existing WikEmacs texts are under GFDLv1.3+<br />
<br />
For emacswiki.org, we could either ask them to specify their version(s) of GFDL, or we could use their text under their simple permissive licence. If we do the latter, we could include a mention of their copyright notice either in the default copyright notice at the bottom of all WikEmacs pages, or we could create a template "''This page includes text from emacswiki.org, used under [http://www.emacswiki.org/OLD this licence]''".<br />
<br />
For the GNU Emacs manual, if we're going to continue using GFDLv1.3+, then we don't have to do anything. But if we want to switch to the dual-licence model used by Wikipedia (and accepted by Stallman), then whenever we copy text from the manual, we'd have to put a template on those pages to say that those pages are only available under GFDLv1.3+ (and not CC-sa).<br />
<br />
For text by WikEmacs contributors, we could continue to license it under GFDLv1.3+, or we could say that from now on, contributions are under the Wikipedia-style dual-licence (GFDLv1.3+ and CC-sa). This wouldn't change much but it would give us more options in the future if we do encounter problems.<br />
<br />
I'll have to think for a while before having any recommendations, and there's currently nothing messy or problematic, but just wanted to note the situation early on in case anyone wants to make suggestions. I have experience with licensing issues. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:02, 23 April 2013 (EDT)<br />
<br />
: I have spent some time thinking on this, and your suggestion of asking emacswiki.org to clarify their version of GFDL appears to be simplest. That way WikEmacs could maintain its current GFDLv1.3+ license and no ugly licensing notices would be necessary when porting content from emacswiki.org, assuming thes choose GFDLv1.3+. In the event they choose a different version of GFDL, is it possible to port old versions of the license to new versions so we could use the material under GFDL1.3+? --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 13:30, 3 May 2013 (EDT)<br />
<br />
::Ok, I've thought through the scenarios now. The current Wikemacs licence notice is fine: if wikemacs contains original content plus emacswiki content plus GNU manual content plus Wikipedia content, it will always be true that the recipient can distribute under GFDL v1.3 or any later version. (emacswiki doesn't textually say "v1.3+" but all their pages are also under a [http://www.emacswiki.org/OLD do what you want, just preserve our copyright notice] licence, so GFDL version ambiguities can be ignored.) So nothing has to be changed in the footer.<br />
<br />
::The two other issues are the copyright details, and the licence of original contributions.<br />
<br />
::Copyright details. If we include material from the manual/wikipedia/emacswiki, then we have to mention this somewhere (otherwise we'd be claiming to own stuff we copied from them). At a minimum, we have to put a general statement in [[WikEmacs:Copyrights]] to say "''Some pages incorporate text from XYZ, received under <copy of their licence notice>''".<br />
<br />
::Legally, that's all that's necessary. But, by lacking precision it leads to certain inconveniences. For example, if someone wants to copy an article from here that contains just original content, they should be able to include just a single line "''copyright 2013 Wikemacs''", but if there's no way to see that it's original content then that person will have to include all the "''this may contain...''" statements from [[WikEmacs:Copyrights]]. Or if there's a problem later (such as someone adding non-free content to emacswiki, and us copying it over), we're left with a mess not knowing what pages have to be checked/reverted.<br />
<br />
::(This reminds me that the copyright situation of my own wiki is not a shining example, but that's less problematic since all material is original content.)<br />
<br />
::So, for keeping track of copyrights, nothing is ''required'' and complexity just makes people less likely to do it, so it's just a matter of picking the low hanging fruit. I see four possibilities:<br />
::# Mention "''from XYZ''" in the edit summary. Drawback: if someone forgot to do this, there's no way to go back later and put it into the edit summary, and, the only way to search all edit summaries is by going to each page... tedious.<br />
::# Mention it on the page. This is what wikipedia does. Make a template so that editors can add <nowiki>{{</nowiki>copyright manual}} to the bottom of the page or in the "References" section to add one sentence "''This page incorporates bla bla see [[WikEmacs:Copyrights]]''".<br />
::# Same, but put it at the top of the Talk: page.<br />
::# Make a page for listing which pages contain substantial amounts of material from what sources.<br />
::The last two look nice and clean but that's also a drawback since if reader-contributors don't see how copyright info is noted, they won't realise that they should also make a note when they add third-party content to a page. The second solution adds a bit of mess to the page, but it works well with the wiki model of learn-by-copying.<br />
<br />
::If in doubt, I'd go with the second option. (Copying Wikipedia is usually a safe move.) We can always change at a later stage.<br />
<br />
::The last thing is the licence of new contributions (i.e. what should the notice under the edit box say "''all contributions to WikEmacs are considered to be released under...''"). My usual reflex is to use GNU whatever, but Stallman did give Wikipedia the green light to move to a dual GFDL + CC-by-sa for original contributions. I can't remember all the problems that motivated Wikipedia to migrate, but I think there were some issues like GFDL's requirement to include a copy of the licence when distributing covered works (so when you print a 2-page article, you have to add the 10 pages of the licence). Copying Wikipedia's approach probably has some practical advantages for people re-using Wikemacs material, and it allows people to copy material from Wikemacs into Wikipedia (while still being able to copy wikemacs material into the GNU manuals etc.). So for new contributions, a plain GFDLv1.3+ is fine, but the Wikipedia model is probably better. This wouldn't change the footer - GFDL would still be our primary licence since some pages would combine original content (GFDL+CC-by-sa) with content from the GNU manual (GFDL only) and the combination could only be distributed under GFDL, not CC-by-sa.<br />
<br />
::It would also be a good idea for the notice under the edit box to tell people "''If you incorporate material from the GNU manual, please include <nowiki>{{</nowiki>copyright manual}} at the end of the page''", and similar for emacswiki and Wikipedia.<br />
<br />
::Hope that helps. I'll be back at the end of June. None of this is urgent anyway. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 07:27, 3 June 2013 (EDT)<br />
<br />
== Which emacswiki.org topics to work on? ==<br />
<br />
So, for each of the useful pages on emacswiki.org, we should make our own pages for those topics and incorporate the knowledge that's in the emacswiki.org pages, but how do we make a list of the useful emacswiki.org pages?<br />
<br />
Does the site have any equivalents to MediaWiki's pages:<br />
<br />
* [[Special:LongPages]]<br />
* [[Special:MostLinkedPages]]<br />
* [[Special:MostRevisions]]<br />
<br />
? (But IMO we should take a decision on the licence before doing a lot of work.) [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 12:27, 24 April 2013 (EDT)<br />
<br />
:If not, I wonder if search engines could help us approximate the "value" of each page?<br />
<br />
:* https://www.google.com/search?q=site%3Aemacswiki.org<br />
<br />
:Hmm. I'd take that as a no. Looks like a random selection. Any other ideas?<br />
<br />
:Finding the pages with the most revisions shouldn't be too hard. Just involves a script downloading the history of [http://www.emacswiki.org/emacs/?action=printable-index each page] and sorting by length. That might give an indication of the good pages.<br />
<br />
:The [http://www.alexa.com/siteinfo/emacswiki.org info on alexa.com] isn't too solid, but gives some hints about what people look for. [[User:Ciaran|Ciaran]] ([[User talk:Ciaran|talk]]) 11:19, 3 June 2013 (EDT)<br />
::I will look into this. In the mean time, I would edit articles whenever you cannot you find the information you want on the wiki. This is how I edit wikis in general. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 22:07, 26 November 2013 (EST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47481Emacs Terminology2016-05-29T14:32:21Z<p>Holocronweaver: /* font-lock */ remove test</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting.<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47480Emacs Terminology2016-05-29T14:32:05Z<p>Holocronweaver: /* font-lock */</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting. Test.<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Talk:Emacs_Terminology&diff=47475Talk:Emacs Terminology2016-05-27T23:46:56Z<p>Holocronweaver: Reverted edits by Holocronweaver (talk) to last revision by Francesco</p>
<hr />
<div>== Split? ==<br />
Should we split this page into two parts? For example the first part would deal with Emacs' key concepts (frame, window, buffer, modes, point, region, ...), while another part would deal with text editing features (killing/yanking, filling, narrowing/widening, ...)? [[User:Francesco|Francesco]] 17:09, 28 March 2012 (EEST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=Talk:Emacs_Terminology&diff=47474Talk:Emacs Terminology2016-05-27T23:46:40Z<p>Holocronweaver: </p>
<hr />
<div>== Split? ==<br />
Should we split this page into two parts? For example the first part would deal with Emacs' key concepts (frame, window, buffer, modes, point, region, ...), while another part would deal with text editing features (killing/yanking, filling, narrowing/widening, ...)? [[User:Francesco|Francesco]] 17:09, 28 March 2012 (EEST)<br />
<br />
This is test text.</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47473Emacs Terminology2016-05-27T23:45:58Z<p>Holocronweaver: /* font-lock */ remove test text</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting.<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47472Emacs Terminology2016-05-26T15:19:19Z<p>Holocronweaver: /* font-lock */</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting. nothing<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47471Emacs Terminology2016-05-25T17:32:38Z<p>Holocronweaver: Reverted edits by Holocronweaver (talk) to last revision by Ciaran</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting.<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Emacs_Terminology&diff=47470Emacs Terminology2016-05-25T17:32:22Z<p>Holocronweaver: /* font-lock */</p>
<hr />
<div>[[File:Emacs_parts.png|320px|thumb|right|different color boxes shows different parts of emacs frame]]<br />
== Buffer ==<br />
<br />
When you use {{Keys|C-x C-f}} to invoke command find-file, Emacs opens the file you request, and puts its contents into<br />
a buffer with the same name as the file. Instead of thinking that you are editing a file, think that you are editing<br />
text in a buffer. When you save the buffer, the file is updated to reflect your edits.<br />
<br />
Buffers can also contain text that doesn't come from a file. When you use {{Keys|C-x C-b}} to get a list of buffers,<br />
that list is itself in a buffer, called <tt>*Buffer List*</tt>, and that buffer is not associated with any file.<br />
<br />
By convention, buffers whose names start with an asterisk ('''`*'''') are not associated with files (but that doesn't<br />
mean you can't save them in files). If they have unsaved changes when you exit Emacs, these buffers are killed without<br />
your being asking for confirmation.<br />
<br />
Buffers whose names start with a space are [[InvisibleBuffers|invisible]] to many operations. These are generally<br />
internal buffers that you don't want to see. Their names normally don't appear in the buffer list or as<br />
[[Completion|completion]] candidates when you switch buffers using {{Keys|C-x b}}.<br />
<br />
Buffers are shown in [[#Window|windows]]. You can have more than one window showing the same buffer. {{Keys|C-x 2}}<br />
splits the current window, creating two windows, both showing the same buffer.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Buffers|Buffers}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
<br />
<br />
== Window ==<br />
<br />
In Emacs terminology, a "window" is a container in which a [[#Buffer|buffer]] is displayed. This may be confusing at first; if so, think "pane" whenever you see "window" in an Emacs context until you get used to it.<br />
<br />
A new Emacs [[#Frame|frame]] contains one window. This window can be split in to multiple windows using:<br />
* {{CommandKeys|C-x 2|split-window-below}} - Split the window horizontally to create two stacked windows<br />
* {{CommandKeys|C-x 3|split-window-right}} - Split the window vertically to create two side-by-side windows<br />
<br />
You can use multiple windows to view different [[#Buffer|buffers]] (or different portions of the same [[#Buffer|buffer]]) at once.<br />
<br />
You can read more about windows in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Windows|Windows}}<br />
<br />
== Frame ==<br />
<br />
In Emacs terminology, a "frame" is what most window managers (Windows, OSX, GNOME, KDE, etc.) would call a "window".<br />
<br />
It will typically have a title bar and some buttons to iconify (minimize), maximize / restore, and close the frame. To<br />
see an example, open up a second frame from your running Emacs instance with {{CommandKeys|C-x 5 2|make-frame-command}}. You can close frames with {{CommandKeys|C-x 5 0|delete-frame}}, though this<br />
will not close the last frame that is open.<br />
<br />
To be completely correct, frames can be created when Emacs is running in terminal mode too, not just in a windowing system. They don't provide the same visual cues but otherwise work the same.<br />
<br />
<br />
You can read more about frames in the Emacs manual:<br />
* {{Manual|emacs|Screen|Screen}}<br />
* {{Manual|emacs|Frames|Frames}}<br />
<br />
== Point ==<br />
<br />
The active cursor shows the location at which editing commands will<br />
take effect, which is called "point". Many Emacs commands move<br />
point to different places in the buffer; for example, you can place<br />
point by clicking mouse button 1 (normally the left button) at the<br />
desired location.<br />
<br />
If you use a block cursor, the cursor appears to be on a<br />
character, but you should think of point as between two characters;<br />
it points before the character that appears under the cursor. For<br />
example, if your text looks like `frob' with the cursor over the `b',<br />
then point is between the `o' and the `b'. If you insert the character<br />
`!' at that position, the result is `fro!b', with point between the `!'<br />
and the `b'. Thus, the cursor remains over the `b', as before.<br />
<br />
Sometimes people speak of "the cursor" when they mean "point," or<br />
speak of commands that move point as "cursor motion" commands.<br />
<br />
<br />
You can read more about the point in the Emacs manual:<br />
* {{Manual|emacs|Point|Point}}<br />
<br />
<br />
<br />
== The Mark and the Region ==<br />
<br />
Many Emacs commands operate on an arbitrary contiguous part of the<br />
current buffer. To specify the text for such a command to operate on,<br />
you set "the mark" at one end of it, and move point to the other end.<br />
The text between point and the mark is called "the region". The region<br />
always extends between point and the mark, no matter which one comes<br />
earlier in the text; each time you move point, the region changes.<br />
<br />
<br />
You can read more about the mark and the region in the Emacs manual:<br />
* {{Manual|emacs|Mark|Mark}}<br />
<br />
<br />
<br />
== Killing ==<br />
<br />
In Emacs, "killing" means erasing text and copying it into the "kill<br />
ring". "Yanking" means bringing text from the kill ring back into the<br />
buffer. (Some applications use the terms "cutting" and "pasting" for<br />
similar operations.) The kill ring is so-named because it can be<br />
visualized as a set of blocks of text arranged in a ring, which you can<br />
access in cyclic order.<br />
<br />
<br />
You can read more about killing in the Emacs manual:<br />
* {{Manual|emacs|Killing|Killing}}<br />
<br />
<br />
<br />
== Yanking ==<br />
<br />
"Yanking" means reinserting text previously killed. The usual way to<br />
move or copy text is to kill it and then yank it elsewhere one or more<br />
times.<br />
<br />
You can read more about Yanking in the Emacs manual:<br />
* {{Manual|emacs|Yanking|Yanking}}<br />
<br />
<br />
<br />
== Faces ==<br />
<br />
Emacs can display text in several different styles, which are called faces. Each face can specify various face attributes, such as the font, height, weight and slant, the foreground and background color, and underlining or overlining. A face does not have to specify all of these attributes; often it inherits most of them from another face.<br />
<br />
On a text-only terminal, not all face attributes are meaningful. Some text-only terminals support inverse video, bold, and underline attributes; some support colors. Text-only terminals generally do not support changing the height, width or font.<br />
<br />
Most major modes assign faces to the text automatically through the work of Font Lock mode. See Font Lock, for more information about Font Lock mode and syntactic highlighting. You can print the current buffer with the highlighting that appears on your screen using the command {{Command|ps-print-buffer-with-faces}}. <br />
<br />
<br />
You can read more about faces in the Emacs manual:<br />
* {{Manual|emacs|Faces|Faces}}<br />
<br />
<br />
<br />
== Major mode ==<br />
<br />
Emacs can adapt its behaviour to the specific type of text edited in a buffer. The set of specific Emacs customizations for a particular type of text is called a "major mode". Each buffer has exactly one major mode depending on its content type (but see [[MuMaMo]] for a way to relax this constraint).<br />
<br />
Major modes can change the meaning of some keys, define syntax highlighing or indentation rules, and install new key bindings (usually beginning with {{Keys|C-c}}) for mode-specific commands. Emacs ships with a wide range of major modes, falling into three main categories:<br />
* support for text (e.g. [[:Category:Markup languages|markup languages]]),<br />
* support for [[:Category:Programming languages|programming languages]],<br />
* applications within emacs (e.g. [[dired]], [[gnus]], ...). Buffers using this last group of major modes are usually not associated to files, but rather serve as a user interface.<br />
<br />
<br />
You can read more about major modes in the Emacs manual:<br />
* {{Manual|emacs|Major-Modes|Major Modes}}<br />
<br />
== Minor mode ==<br />
<br />
Minor modes are optional features that can be turned on and off. Minor modes can be enabled for specific buffers (''buffer-local'' modes) or all buffers (''global'' modes). <br />
<br />
Emacs provides lots of minor modes. Just a few examples:<br />
<br />
* [[Auto Fill]] mode to automatically [[#Fill]] text as you type.<br />
* [[Flyspell]] mode to highlight spelling errors as you type.<br />
* [[Visual Line]] mode to wrap long lines to fit the screen. (See [[#Screen Lines]])<br />
* [[Transient Mark]] mode to highlight the current region.<br />
<br />
You can read more about minor modes in the Emacs manual:<br />
* {{Manual|emacs|Minor-Modes|Minor Modes}}<br />
<br />
== Fill ==<br />
<br />
In Emacs ''filling'' text means breaking it in to lines of a given maximum width. You can enable automatic filling with {{Command|auto-fill-mode}}, or fill a specific block of text using something like {{CommandKeys|M-q|fill-paragraph}}.<br />
<br />
Note that fill commands add hard line breaks to the text. This is different from what might be called "word wrap" (or "line wrap") in other tools, where the text is wrapped at the edge of the current display and re-flowed if the window is resized. Emacs provides this sort of wrapping as well, see [[#Screen Lines]]<br />
<br />
You can read about the various ways to fill text in the Emacs manual:<br />
* {{Manual|emacs|Filling|Filling}}<br />
<br />
== Screen Lines ==<br />
<br />
Emacs provides several ways to deal with text lines that extend horizontally beyond the size of the current window. These are display features: they change the ''screen lines'' shown in the window without modifying the ''logical lines'' of the actual text. <br />
<br />
* By default, Emacs wraps a long line of text at the edge of the window and shows the remaining text in ''continuation lines''.<br />
* [[Visual Line]] mode provides what is commonly called "word wrap": long lines are wrapped at the edge of the window without breaking in the middle of a word. Try {{Command|visual-line-mode}}.<br />
* ''Line truncation'' means that text beyond the edge of the display is simply not shown, i.e. the line is cut off. Try {{Command|toggle-truncate-lines}}.<br />
<br />
These display options can affect how some editing and movement commands work. Refer to the documentation for details. To reformat text with hard line breaks, see [[#Fill]]. <br />
<br />
You can read more about the various ways of visualizing long lines in the Emacs manual:<br />
* {{Manual|emacs|Continuation-Lines|Continuation Lines}}<br />
* {{Manual|emacs|Visual-Line-Mode|Visual Line Mode}}<br />
* {{Manual|emacs|Line-Truncation|Line Truncation}}<br />
<br />
<br />
== case-fold ==<br />
<br />
Case '''in'''sensitivity.<br />
<br />
== Narrow and widen ==<br />
<br />
Sometimes you want to work on just a portion of the current buffer and ignore the rest. Emacs provides commands to ''narrow'' the display so that it only shows the text you are interested in. Text outside of the current ''restriction'' is hidden from view and inaccessible to editing commands. <br />
<br />
Use {{CommandKeys|C-x n n|narrow-to-region}} to narrow the display to the current region. Use {{CommandKeys|C-x n w|widen}} to ''widen'' the display, making the entire buffer accessible again. <br />
<br />
Note that narrowing can be confusing to new users, so the command <tt>narrow-to-region</tt> is disabled by default. If you have not explicitly enabled this command before trying to use it, you will be prompted to do so.<br />
<br />
Narrowing can be considered an alternative to collapsing blocks of text (folding). Narrowing allows you to identify a block of text to edit, whereas folding allows you to identify a block of text to hide. Emacs has various ways to hide text (see [[#Selective Display]]). The key difference between hiding text and narrowing is that hidden text remains editable: you can still delete a block of text that has been collapsed from view. With a narrowing restriction, only the active text can be modified. <br />
<br />
You can read more about narrowing and other ways to hide text in the Emacs manual:<br />
* {{Manual|emacs|Narrowing|Narrowing}}<br />
<br />
== Selective Display ==<br />
<br />
Emacs provides a way to hide lines of text indented more than a given number of columns:<br />
{{Command|set-selective-display}}, bound to {{Keys|C-x $}} by default. <br />
<br />
This can be useful to hide "details" and get an overview of a file that uses indentation in some meaningful way (like most programming langauges). Note that the hidden text remains editable; see [[#Narrowing]] for a safer way to edit a specific portion of a buffer.<br />
<br />
There are a variety of other ways to hide text in an Emacs buffer, such as [[Outline]] and [[Hideshow]] modes.<br />
<br />
You can read more about selective display in the Emacs manual:<br />
* {{Manual|emacs|Selective-Display|Selective Display}}<br />
<br />
[[Category:Beginner]]<br />
<br />
== font-lock ==<br />
<br />
Syntax highlighting.Test.<br />
<br />
[[Category:Key Concepts]] [[Category:Emacs Terminology]] [[Category:Beginner]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Sandbox&diff=47469Sandbox2016-05-25T14:26:46Z<p>Holocronweaver: </p>
<hr />
<div>.<br />
aonestuhaoesnutaohesunatoehusn</div>Holocronweaverhttps://wikemacs.org/index.php?title=Sandbox&diff=47468Sandbox2016-05-25T14:26:35Z<p>Holocronweaver: Created page with "."</p>
<hr />
<div>.</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=47248Main Page2016-04-13T21:34:02Z<p>Holocronweaver: remove balloon image</p>
<hr />
<div>'''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** 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.''<br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Main_Page&diff=47241Main Page2016-03-22T23:33:52Z<p>Holocronweaver: </p>
<hr />
<div>[[File:InflatableBalloons.jpg|50px|left]] '''WikEmacs''' is here to stay. Spread the word!<br />
<br />
[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]<br />
__NOTOC__<br />
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.<br />
<br />
-----------<br />
We need more '''[[:Category:WikEmacs Contributor|WikEmacs contributors]]'''. You can help the following way.<br />
<br />
{{Note| First of all, please take a minute to look at the<br />
[[WikEmacs:Guidelines|WikEmacs guidelines]] before you start editing.}}<br />
<br />
* Priority tasks<br />
** 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.''<br />
* Intermediate tasks<br />
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].<br />
** Add more content to [[Special:ShortPages|short pages]].<br />
** Document or add more [[:Category:Third Party Package|third party packages]].<br />
* Other tasks<br />
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.<br />
** Add more members to various [[Special:Categories|categories]].<br />
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].<br />
<br />
----<br />
'''Emacs News'''<br />
<br />
The latest stable release of Emacs is [[GNU Emacs 24|Emacs-24.5]].<br />
<br />
Emacs is available on all popular [[:Category:Install Or Upgrade| operating systems]] including [[Installing Emacs on BSD |BSD]], [[Installing Emacs on GNU/Linux | GNU/Linux]], [[Installing Emacs on OS X | OS X]] and [[Installing Emacs on Windows| Windows]]. It supports a variety of [[:Category:Programming languages|programming languages]].<br />
<!-- Left hand column --><br />
<div style="float: left; width: 49%;"><br />
== Explore WikEmacs ==<br />
<br />
To explore WikEmacs proceed as follows:<br />
* Search for or visit a page of interest<br />
* At the end of the page, there is a list of categories<br />
* Click on individual categories and it will give you a list of all pages that will be of interest to you.<br />
<br />
=== What is your comfort level with Emacs? ===<br />
* [[:Category:Beginner|Beginner]]<br />
* [[:Category:Intermediate|Intermediate]]<br />
* [[:Category:Expert|Expert]]<br />
** 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 can write about your package as well as you.<br />
** Have you developed any [[:Category:Third Party Package|Third Party Package]]s? Consider writing about what it is and how to use it.<br />
* [[:Category:Vim User|Vim User]]<br />
<br />
=== What do you want to accomplish now? ===<br />
* [[:Category:Install Or Upgrade|Install Or Upgrade]]<br />
* [[:Category:Customization|Customize Emacs]]<br />
* [[Key Bindings|Tweak Key Bindings]]<br />
* [[:Category:Tutorial|Learn more Emacs (Tutorials)]]<br />
* [[:Category:Emacs Lisp|Learn Emacs Lisp]]<br />
<br />
=== What do you use Emacs for? ===<br />
* [[:Category:Text Editing|Text Editing]]<br />
* [[:Category:Programming|Programming]]<br />
* [[:Category:Document authoring|Document authoring]]<br />
* [[:Category:Organizer|Getting Organized]]<br />
* [[:Category:Email|Emailing]]<br />
* [[:Category:Chat|Chatting]]<br />
* [[:Category:Blog|Blogging]]<br />
* [[:Category:Browse|Browsing]] <br />
* [[:Category:Entertainment|Entertainment]]<br />
* [[:Category:Workflow|Other]]<br />
<br />
=== How do you involve yourself with the community? ===<br />
* [[:Category:Emacs User|Emacs User]]<br />
* [[:Category:Emacs Contributor|Emacs Contributor]]<br />
* [[:Category:WikEmacs Contributor|WikEmacs Contributor]]<br />
* [[:Category:User Role|Other]]<br />
<br />
</div><br />
<!-- Right hand column --><br />
<div style="float: right; width: 49%;"><br />
<br />
==Help build WikEmacs==<br />
<br />
The following are suggestions for articles to write, along with the page of the GNU Emacs manual which documents this feature. ('''Note:''' it's possible that an article for a given topic exists already under a different name. In that case, please ensure that the article includes the link to the manual page, and then remove the topic from this list.)<br />
<br />
<!-- Not finished. I grabbed ideas from large section titles of the manual, but there are many more in the "Detailed Node Listing", longer version of the table of contents. --><br />
<br />
* [[Command-line startup options]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Entering-Emacs.html] and [https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Invocation.html])<br />
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])<br />
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])<br />
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])<br />
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])<br />
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])<br />
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])<br />
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])<br />
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])<br />
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])<br />
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])<br />
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])<br />
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])<br />
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])<br />
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])<br />
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])<br />
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])<br />
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])<br />
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])<br />
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])<br />
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])<br />
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])<br />
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])<br />
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])<br />
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])<br />
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])<br />
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])<br />
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])<br />
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])<br />
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])<br />
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])<br />
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])<br />
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])<br />
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])<br />
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])<br />
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])<br />
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])<br />
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])<br />
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])<br />
<br />
<br />
[[Category:WikEmacs]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47240User:Holocronweaver2016-02-29T04:55:09Z<p>Holocronweaver: /* TODO */</p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* fix RSS feed<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the homeless pet captcha, has been closed down in Dec 2014 - hopefully something similar will sprout up<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]<br />
<br />
[[Category:WikEmacs Contributor]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Keyboard_macros&diff=47221Keyboard macros2016-01-25T01:20:04Z<p>Holocronweaver: Revert to the last reasonable edit.</p>
<hr />
<div>{{Manual|emacs|Basic-Keyboard-Macro|Basic Keyboard Macro}}<br />
<br />
'''Keyboard macros''' can be used to automate or repeat tedious editing tasks in Emacs.<br />
<br />
<br />
==Basic Use==<br />
<br />
; {{Keys|F3}}, or {{Keys|C-x (}}<br />
: Start defining a macro.<br />
; {{Keys|F4}}, or {{Keys|C-x )}}<br />
: Stop defining a macro.<br />
; {{Keys|F4}}, or {{Keys|C-x e}}<br />
: Execute a macro<br />
; {{Keys|C-u 37 C-x e}} or {{Keys|C-u 37 F4}}<br />
: Execute a macro multiple times, using [[prefix argument]]<br />
; {{Keys|C-u 0 C-x e}}<br />
: Execute a macro until the end of the buffer<br />
<br />
==Example usage==<br />
<br />
Consider the standard <code>*scratch*</code> buffer:<br />
<br />
<pre><br />
;; This buffer is for notes you don't want to save, and for Lisp evaluation.<br />
;; If you want to create a file, visit that file with C-x C-f,<br />
;; then enter the text in that file's own buffer.<br />
</pre><br />
<br />
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.<br />
<br />
# Make sure [[point]] is at the start of the buffer.<br />
# 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.<br />
# 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.<br />
# Hit backspace to delete that "a".<br />
<br />
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.<br />
<br />
<ol start="5"><br />
<li>Hit <code>C-e C-f</code> to move point to the beginning of the next line.</li><br />
<li>Hit <code>C-x )</code> to finish the recording of our macro.</li><br />
</ol><br />
<br />
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.<br />
<br />
<ol start="7"><br />
<li>Hit <code>C-x e</code> once to call that macro.</li><br />
<li>Continue hitting <code>e</code> to call it several times. Hit any other key to get out of the macro repetition.</li><br />
</ol><br />
<br />
== Naming and saving macros ==<br />
<br />
You can:<br />
* give a name to the most recently defined macro (<code>C-x C-k n</code>)<br />
* bind it to a key sequence (<code>C-x C-k b</code>)<br />
* insert it in the current buffer as lisp code (<code>M-x insert-kbd-macro</code>).<br />
<br />
{{Manual|emacs|Save-Keyboard-Macro|Save Keyboard Macro}}<br />
<br />
<br />
To bind a keyboard macro to a key use <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.<br />
<br />
==Variables==<br />
<br />
Variables can be stored in lisp or in [[registers]]. Here's an example using lisp:<br />
<br />
<pre><br />
[M-: (setq x 1)]<br />
<F3><br />
Line number [C-u M-: x]<br />
[M-: (setq x (+ x 1))]<br />
<F4><br />
</pre><br />
<br />
Now execute the macro four times with the command <code>C-x e e e e</code> and you get:<br />
<br />
line number 1<br /><br />
line number 2<br /><br />
line number 3<br /><br />
line number 4<br />
<br />
<br />
= See also =<br />
<br />
* [https://github.com/Silex/elmacro elmacro], to show keyboard macros as emacs-lisp<br />
* [https://github.com/abo-abo/centimacro centimacro] to (temporarily) bind any number of macros to any global shortcuts.<br />
* You can use keyboard macros à la vim in [[evil]].<br />
<br />
<br />
[[Category:Intermediate]]<br />
[[Category:Editing]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Keyboard_macros&diff=47220Keyboard macros2016-01-25T01:18:53Z<p>Holocronweaver: Revert a bunch of vandalism.</p>
<hr />
<div>= Keyboard Macros =<br />
<br />
Start keyboard macro recording: <br />
<br />
[ C-x ( ]<br />
<br />
End keyboard macro recording:<br />
<br />
[ C-x ) ]<br />
<br />
Execute keyboard macro recorded:<br />
<br />
[ C-x e ]<br />
<br />
Execute many 10 times recorded keyboard macro:<br />
<br />
[ C-u 10 ][ C-x e ]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Keyboard_macros&diff=47219Keyboard macros2016-01-25T01:17:54Z<p>Holocronweaver: Reverted edits by 93.188.39.246 (talk) to last revision by 94.102.51.31</p>
<hr />
<div>精准医疗又叫个性化医疗,是指以个人基因组信息为基础,结合蛋白质组,代谢组等相关内环境信息,为病人量身设计出最佳治疗方案,以期达到治疗效果最大化和副作用最小化的一门定制医疗模式。因此相较传统医疗,精准医疗具有针对性、高效性及预防性等特征。 <br />
<br />
美国医学界在2011年首次提出了“精准医学”的概念,今年1月20日,奥巴马又在美国国情咨文中提出“精准医学计划”,希望精准医学可以引领一个医学新时代。10月8日,2015全球创新论坛纽约峰会在纽约穆迪总部大楼举办。乐土投资集团CEO刘如银在峰会上介绍了他的精准医疗生态圈的想法。 <br />
<br />
刘如银介绍了乐土投资在美国的国际化实践,包括在美国的地产投资拓展,以及最新投资的医疗健康项目。乐土投资集团(CLIG)定位以硅谷的高科技投资为引擎,以科技医疗和互联网金融为两翼,链接最具价值的深科技健康项目,服务国际大健康和科技发展。 <br />
<br />
美国财政预算计划在2016年拨付给美国国立卫生研究院(NIH)、美国食品药品监督管理局(FDA)、美国国家医疗信息技术协调办公室(ONC)等机构共2.15亿美元用于资助这方面的科学研究与创新发展。 <br />
<br />
刘如银说:美国的精准医疗主要是围绕着基因组、蛋白组等方面的检测,也就是围绕分子生物学的特性,针对个体化的病理特征进行治疗。而我们所关注的不仅如此,更是系统化的,全过程、全要素、全局性的对医疗过程和临床实践进行优化。我们所指的精准医疗也是针对每一个病人的具体病情,正确选择并精确的应用适当的治疗方法。刘如银认为:精准医疗的最终目标是以最小化的医源性损害、最低化的医疗资源耗费去获得最大化的病患的效益,其前景不可限量。 <br />
<br />
精准医疗要做到个性、高效及预防的关键在于筛查和诊断,因此基因测序等检测诊断技术的发展是关键。成本的下降让基因测序商业化市场的打开成为可能,基因测序技术的成熟和商用经过了多年的发展,1980 年自动测序仪出现,2001 年完成了人类基因组框架图标志着这一技术的成熟,2007 年二代基因测序技术大幅降低测序成本,使得这一技术应用出现可能,以走在前列的Illumina 公司为例,该公司自2007 年起把当时每个基因组的测序成本费用从1000万美元降到了当下的1000 美元, 根据Illumina 公司数据,全球NGS(二代基因测序)的应用市场规模预计为200 亿美元,药品研发和临床应用是增速最快的领域,增速超过15%,肿瘤诊断和个性化用药是最有应用前景的领域,市场规模120亿美元。乐土投资与Illumina以及新一代的基因检测公司Genalyte, Centrillion都有着合作关系。 <br />
<br />
刘如银说:精准医疗作为医疗模式的革新对提高我国国民健康水平有重要意义,将在基因测序技术发展和国家政策的推动下迎来黄金发展期。精准治疗是下一个新兴朝阳行业,我们关注基因测序、肿瘤诊断及个性化用药等相关投资机会。 <br />
<br />
全球创新论坛纽约峰会由全美华人金融协会(The Chinese Finance Association, TCFA) 主办。全美华人金融协会于一九九四年在美国成立。分布在世界各地的会员来自华尔街投行、基金、监管部门、和学术界,已成为联系中美金融界最重要的桥梁之一。协会定期举行学术年会。协会本部设在纽约,并在波士顿,华盛顿,旧金山,伦敦,香港,北京和上海等金融中心设有分会。 <br />
<br />
原招商银行行长马蔚华,中信银行美国分行行长文兵,汉世纪投资管理有限公司合伙人吴皓,联合国南南合作办首席经济与投资专家杨庆宏等参加了本年度会议并发表了讲话。</div>Holocronweaverhttps://wikemacs.org/index.php?title=User_talk:Holocronweaver&diff=47218User talk:Holocronweaver2016-01-25T01:17:03Z<p>Holocronweaver: </p>
<hr />
<div>Hello, Holocronweaver, I am new to WikEmacs. Any chance we could get http://wikemacs.org/index.php/Keyboard_macros protected?<br />
<br />
: Done. --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 21:00, 21 November 2013 (EST)<br />
<br />
== What is the policy about non-English articles? ==<br />
<br />
I found this page in Chinese:<br />
<br />
[[Keyboard_macros]]<br />
<br />
I'm not interested in running it through a translator and seeing what's usable, so I would delete it without mercy.<br />
<br />
I did check [[WikEmacs:Guidelines]], but didn't see any indication of a policy on this matter.<br />
<br />
Are there guidelines about non-English contributions?<br />
<br />
Thanks.<br />
<br />
: Sorry for slow response. I can actually read some Chinese, and what is posted there is spam for a Chinese biotech company. It is useless, so I reverted it. I did not realize we had a Guidelines page, good to know! I will look into adding multi-language support, but it may take a couple months. Until then, if you come across non-English text you think is worth preserving, copy it here and mention the source article. I will get it added to its appropriate language page once support is added. Thanks! --[[User:Holocronweaver|Holocronweaver]] ([[User talk:Holocronweaver|talk]]) 20:17, 24 January 2016 (EST)</div>Holocronweaverhttps://wikemacs.org/index.php?title=Category:Emacs_Lisp&diff=47107Category:Emacs Lisp2015-09-14T00:52:36Z<p>Holocronweaver: restore original contentns</p>
<hr />
<div>'''Emacs Lisp''' is special for Emacs. So an additional category.<br />
<br />
[[Category:Programming languages]]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Category:Emacs_Lisp&diff=47106Category:Emacs Lisp2015-09-14T00:50:21Z<p>Holocronweaver: Reverted edits by 188.126.91.88 (talk) to last revision by 188.126.90.202</p>
<hr />
<div>In {{a small|a little|a tiny} number|a handful} of {case|situation|instance} {reports|records}, {substantial|considerable|significant|sizable} {increases|boosts|rises} in blood {pressure|stress|tension} #file_links<>links/imp_files/19.08.15.txt",1,S] {have|have actually} been {{attributed|associated|connected} to|credited to|associateded with} {idiosyncratic|distinctive} {reactions|responses} to {estrogens|oestrogens}. In {case|situation|instance} you {get|obtain} {any of|any one of} the {serious|major|severe|significant} {side {effects|results|impacts}|adverse effects|negative effects|negative side effects} {mentioned|discussed|pointed out|stated} - {make {sure|certain}|ensure|make certain|see to it} your {doctor|physician|medical professional} is {notified|informed|alerted} {as {soon|quickly} as|as quickly as|when|as early as} {possible|feasible} {to {prevent|avoid|stop}|to avoid|to stop} #file_links<>links/imp_files/19.08.15.txt",1,S] them from {{getting|obtaining} {worse|even worse}|becoming worse|worsening}. The {symptoms|signs} of {{an allergic|a sensitive} {reaction|response}|an allergy} {include|consist of|feature} {trouble|difficulty|problem} breathing, hives, skin {rash|breakout}, {swollen|inflamed|puffy} lips, {tongue, face and {throat|neck}|tongue, {throat|neck} and face|face, tongue and {throat|neck}|face, {throat|neck} and tongue|{throat|neck}, tongue and face|{throat|neck}, face and tongue}. {If you #file_links<>links/imp_files/19.08.15.txt",1,S] are having these {symptoms|signs} {seek|look for|find} {emergency|emergency situation} {medical|clinical|health care} {assistance|support|help|aid}. |, if you are having these {symptoms|signs} {seek|look for|find} {emergency|emergency situation} {medical|clinical|health care} {assistance|support|help|aid}. {Inform|Notify|Educate} {patients|clients|people|individuals} that they {may|might|could} {occasionally|sometimes|periodically} {see|view} soft {remnants|residues} of Viramune #file_links<>links/imp_files/19.08.15.txt",1,S] XR in their {stool|feces}, which {sometimes|in some cases|often|occasionally} {resemble|look like|appear like} {intact|undamaged|in one piece} {tablets|tablet computers}. {A rapid|A fast|A quick|A swift} return of fertility is likely {following|complying with|adhering to} {treatment|therapy} {with|regarding} Plan B for {emergency|emergency situation} {contraception|birth control}; {therefore|for that reason|as a result|consequently}, {routine|regular|workout} {contraception|birth control} {should|ought to|must|needs to} be {continued|proceeded} or {initiated|started|launched} {as {soon|quickly} as|as quickly as|when} {possible|feasible} #file_links<>links/imp_files/19.08.15.txt",1,S] {following|complying with|adhering to} {use|usage} of Plan B to {ensure|guarantee|make sure|make certain} {ongoing|continuous|recurring} {prevention|avoidance} of {pregnancy|maternity}. Of the 136 {colorectal|intestines} {cancer|cancer cells} {patients|clients|people|individuals} {with|regarding} {grade|quality} 3 or 4 hyperbilirubinemia, 49 {patients|clients|people|individuals} had {grade|quality} 3 or 4 hyperbilirubinemia as #file_links<>links/imp_files/19.08.15.txt",1,S] their last {measured|determined|gauged|assessed} {value|worth}, {of which|which} 46 had liver metastases at {baseline|standard}. As your {body|physical body} {gets|obtains|acquires} #file_links<>links/imp_files/19.08.15.txt",1,S] {used|utilized|made use of} to the {medicine|medication} these {side {effects|results|impacts}|adverse effects|negative effects} {may|might|could} {disappear|vanish|go away}. Lamivudine (EPIVIR) #file_links<>links/imp_files/19.08.15.txt",1,S] {and|and also|as well as} zidovudine (RETROVIR, azidothymidine, AZT, or ZDV) are {synthetic|artificial} nucleoside analogues with {activity|task|tactics} {against|versus} HIV-1. The following {conditions|problems|disorders} are {known|understood} to do that: angina, {congestive heart {failure|failing}|cardiac arrest|heart attack|coronary infarction|heart disease}, {bleeding|hemorrhaging} {disorder|condition|ailment}, heart {{attack|strike}, liver or {kidney|renal|renal system}|{attack|strike}, {kidney|renal|renal system} or liver|liver, {attack|strike} or {kidney|renal|renal system}|liver, {kidney|renal|renal system} or {attack|strike}|{kidney|renal|renal system}, {attack|strike} or liver|{kidney|renal|renal system}, liver or {attack|strike}} {disease|illness|condition}, {{high|very high|higher} or {low|reduced}|{low|reduced} or {high|very high|higher}} blood {pressure|stress|tension}, {inherited|received|acquired} eye {problems|issues|troubles}, {a history|a past|a record} of #file_links<>links/imp_files/19.08.15.txt",1,S] {blood {clots|embolisms}|embolism} or {stroke|movement}, heart {rhythm|tempo} {problems|issues|troubles}, {blood cell|red blood cell} {disorder|condition|ailment}, and {stomach|tummy|belly} {ulcer|abscess|lesion}. Retin-a {should|ought to|must|need to} #file_links<>links/imp_files/19.08.15.txt",1,S] not be {used|utilized|made use of} with sunburn, {eczema|chronic eczema|dermatitis}, or {other|various other} {serious|major|severe|significant} {skin {conditions|problems|disorders}|skin problem|skin issue|skin disease}. This {symptoms|signs} {will|will certainly} {go away|disappear|vanish} as your {continue|proceed} with your {regular|routine|normal} #file_links<>links/imp_files/19.08.15.txt",1,S] {dosing|application} {schedule|routine|timetable}. Medicines are {sometimes|in some cases|often|occasionally} {prescribed|recommended|suggested} for {purposes|functions|objectives} #file_links<>links/imp_files/19.08.15.txt",1,S] {{other|various other} {than|compared to}|besides|aside from|apart from} those {listed|noted|provided|detailed|specified} in a Medication Guide. Norvasc (amlodipine) {belongs to|concerns} the {group|team} of {medicines|medications} called calcium {channel|network|stations} blockers and {works|functions} to {treat|deal with|address|manage} {{high|very high|higher} blood {pressure|stress|tension}|hypertension} and {chest|breast|upper body} {pain|discomfort|ache} by {{slowing|decreasing|reducing} down|decreasing|reducing} your heart #file_links<>links/imp_files/19.08.15.txt",1,S] {rate|price|fee}. It's {important|essential|crucial|vital} to {avoid|prevent|stay clear of|stay away from} oversaturation ({applying|using} {{more|even more|additional} {than|compared to}|greater than} {needed|required|really needed}), as it is not {likely|most likely} to make your #file_links<>links/imp_files/19.08.15.txt",1,S] {acne|acne breakouts|pimples} {{get|obtain} {better|much better}|improve} {sooner|quicker|faster|earlier}. {Note|Keep in mind}: This {page|web page} {contains|includes|consists of|has} #file_links<>links/imp_files/19.08.15.txt",1,S] {side {effects|results|impacts}|adverse effects|negative effects|negative side effects} {data|information} for the {generic|common|universal} {drug|medicine|medication} mefenamic acid. You {will|will certainly} be taking Antabuse {regularly|routinely|frequently|consistently|on a regular basis} for as {long|in length|lengthy} as your #file_links<>links/imp_files/19.08.15.txt",1,S] {doctor|physician|medical professional} {tells|informs} you to. {Some of|A few of|Several of} the {side {effects|results|impacts}|adverse effects|negative effects|negative side effects} that {can|could} {{occur|happen|take place} with|accompany} #file_links<>links/imp_files/19.08.15.txt",1,S] mesalamine {may|might|could} not {need|require} {medical|clinical} {attention|interest|focus}. Do not take this #file_links<>links/imp_files/19.08.15.txt",1,S] {medicine|medication} in {larger|bigger} or {smaller|smaller sized} {amounts|quantities} or for longer {than|compared to} {recommended|suggested|advised}. Erythromycin {can|could} be {used|utilized|made use of} alone #file_links<>links/imp_files/19.08.15.txt",1,S] for them or {combined|incorporated|integrated} with {other|various other} {medications|medicines}. You {{need|require|really need} to|have to|should} {be {aware|conscious|mindful|informed} of|know|understand|recognize} the {fact|truth|reality} some {{mild|moderate|light} and {serious|major|severe|significant}|{serious|major|severe|significant} and {mild|moderate|light}} {side {effects|results|impacts}|adverse effects|negative effects|negative side effects} are #file_links<>links/imp_files/19.08.15.txt",1,S] {possible|feasible}. {Mild|Moderate|Light} {side {effects|results|impacts}|adverse effects|negative effects|negative side effects} are {usually|typically|normally|generally|often} {short-lived|brief|short-term|transient} and {{tend|have a tendency|often tend|usually tend} to|have the tendency to|often} {go away|disappear|vanish} {on their {own|very own}|by themselves|alone} without {any|any type of|any kind of|any sort of} {need|requirement|demand|necessity} for you to {interfere|meddle|conflict} and {treat|address|manage} them {in {any|any type of|any kind of|any sort of} {way|method|means}|by any means|whatsoever}. {Levitra is {a prescription|a prescribed} phosphodiesterase {inhibitor|prevention} you {may|might|could} be {using|utilizing|withing|making use of} if you have {erectile {dysfunction|disorder}|impotence}.|If you have erectile {dysfunction|disorder}, Levitra is {a prescription|a prescribed} phosphodiesterase {inhibitor|prevention} you {may|might|could} be {using|utilizing|withing|making use of}.} {Erectile {dysfunction|disorder}|Impotence} is {a condition|a problem|a disorder} {characterized|defined|identified|distinguisheded} by the {patient|client|person}'s {inability|failure|lack of ability|incapability} {to {get|obtain}|to obtain} {an erection|a construction} of {sufficient|adequate|enough|ample} {hardness|firmness|solidity} and keep it for long {enough|sufficient}. {Patients|Clients|People} {affected|impacted|influenced|had an effect on} {can|could} be {embarrassed|humiliated} #file_links<>links/imp_files/19.08.15.txt",1,S] of the {problem|issue|trouble}, which is {likely|most likely} to {affect|impact|influence|have an effect on} {other|various other} {aspects|facets|elements} of their lives. Elimite is {an efficient|an effective|a reliable} #file_links<>links/imp_files/19.08.15.txt",1,S] anti-parasitic {treatment|therapy|procedure} {used|utilized|made use of} for {patients|clients|people} with scabies and {lice|louse}. Deltasone is {a treatment|a therapy|a procedure} {used|utilized|made use of} for {patients|clients|people} {with|from} {conditions|problems|disorders} that {can|could} #file_links<>links/imp_files/19.08.15.txt",1,S] {cause|trigger|create|induce} {inflammation|swelling|irritation}. Priapism is #file_links<>links/imp_files/19.08.15.txt",1,S] {a dangerous|a harmful|a hazardous|an unsafe|a risky} {side {effect|result|impact}|adverse effects|negative effects|negative side effects} that {may|might|could} {damage|harm|ruin} the {tissues|cells} of your penis. You #file_links<>links/imp_files/19.08.15.txt",1,S] {should|ought to|must|need to} not breast-feed while you are {using|utilizing} this {medicine|medication}. {Tell|Inform} your {doctor|physician|medical professional} {about|regarding|concerning} all {medicines|medications} you #file_links<>links/imp_files/19.08.15.txt",1,S] {use|utilize|make use of}, {and|and also|as well as} those you {start|begin} or {stop|quit} {using|utilizing|making use of} {during|throughout} your {treatment|therapy} with Revatio, {especially|particularly|specifically}.</div>Holocronweaverhttps://wikemacs.org/index.php?title=Keyboard_macros&diff=47105Keyboard macros2015-09-14T00:50:02Z<p>Holocronweaver: Reverted edits by 117.26.249.231 (talk) to last revision by 107.150.42.37</p>
<hr />
<div> 鎴栬€呬綇鍦ㄧ編鍦嬬殑鍛煎彨鍩烘湰 S鏈€濂芥湁涓€榛?濯藉锛屼綘鏈変綘澶皬 浠栧€戠殑鍙h櫉鏄儚璧よ8瑁哥殑浜嬪锛屾洿濂藉湴 鐪熺殑鐪熺殑閭i杭澶氬鍫翠笅闄嶉潪甯告紓浜? <br />
<br />
瀛告牎鐨勬澅瑗匡紝绯荤当纰哄畾閫欐槸鏈€鑱版槑鐨勪簨鎯呯偤浠栧仛 娌掍簨鍏?灏嶆柤鐞冨摗瀹夊痉妫? <br />
<br />
鏄渶濂界殑锛屽洜鐐轰竴鍊嬩汉鎴栧叕鍙哥殑蹇犲绁堟眰杌岄亾 鐒¤珫杈滆緶杈滆緶杈?瀹氫綅鐨勪簨瀵? <br />
<br />
</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47085User:Holocronweaver2015-08-02T18:30:48Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the homeless pet captcha, has been closed down in Dec 2014 - hopefully something similar will sprout up<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47084User:Holocronweaver2015-08-02T18:30:23Z<p>Holocronweaver: /* TODO */</p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
** sadly Asirra, the home pet captcha, has been closed down - hopefully something similar will sprout up<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaverhttps://wikemacs.org/index.php?title=Font&diff=47083Font2015-08-02T17:44:24Z<p>Holocronweaver: </p>
<hr />
<div>'''Fonts''' are a collection of character symbols used to display text. Changing the font used by Emacs will alter the visual appearance of text characters.<br />
<br />
==Customize==<br />
===Buffer===<br />
To customize the font used inside a particular buffer...<br />
===Sessions===<br />
To customize the font used for one or more sessions on a single Emacs installation, use <code>M-x customize-face</code>. Typically you will want to modify the <code>default</code> face.<br />
===.emacs.d===<br />
Fonts can also be configured inside .emacs.d elisp scripts. ...</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47037User:Holocronweaver2015-07-12T18:05:17Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in, probably homeless pets selector (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47036User:Holocronweaver2015-07-12T17:59:56Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
<math>2^2</math><br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in, probably homeless pets selector (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47035User:Holocronweaver2015-07-12T17:59:41Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
2**2<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in, probably homeless pets selector (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaverhttps://wikemacs.org/index.php?title=User:Holocronweaver&diff=47034User:Holocronweaver2015-07-12T17:51:11Z<p>Holocronweaver: </p>
<hr />
<div>Hello! I am the current host of WikEmacs. I want to help create clear, accessible information about Emacs for new and advanced users alike.<br />
<br />
=TODO=<br />
* ✔ use OpenID login<br />
* ✔ make site mobile friendly<br />
* require difficult Captcha for users which are not logged in, probably homeless pets selector (see [https://www.mediawiki.org/wiki/Extension:ConfirmEdit here])<br />
* switch to OpenID Connect<br />
* make OpenID optional<br />
* try out [http://overtone.github.io/emacs-live/ Emacs Live]</div>Holocronweaver