WikEmacs - User contributions [en]

User talk:Ploum

2025-05-26T11:21:41Z

Elvince: hello

Welcome on Wikemacs! [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 11:21, 26 May 2025 (UTC)

Talk:Main Page

2025-03-12T12:49:18Z

Elvince: /* spam: deleteBatch extension? */

== IMPORTANT: Offline discussion ==

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

== IMPORTANT: Content Quality guidelines ==
I think before flame wars and fights among members, we should form
proper/strict guide lines for each aspect of the site. [http://depuypinnaclelawsuit.webnode.com/ DePuy Pinnacle Lawsuit] Wikipedia has very strict
rules about that., even their bots can tell the content quality of a
page. we can create articles in "WikEmacs" Namespace. [[User:Kindahero|Kindahero]] 23:57, 1 April 2012 (EEST)

: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)

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

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

== Markup Conventions==

=== Wikipedia linking convention ===

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

=== EmacsWiki linking convention ===

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

== Describing Modes and Packages ==

=== Naming Conventions ===

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

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

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

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

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

::::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)

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

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

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

== Syntax highlighting ==

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

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

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

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

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

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

: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)

== needed plugins ==

* 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.?

: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)

== WikEmacs staying open? Great! ==

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)

: 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)

:: 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)

== Keeping the licence situation clear and clean ==

Just noting the current situation...

* 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].
* The GNU Emacs manual is published under GFDLv1.3+
* Existing WikEmacs texts are under GFDLv1.3+

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]''".

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).

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.

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)

: 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)

::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.

::The two other issues are the copyright details, and the licence of original contributions.

::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>''".

::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.

::(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.)

::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:
::# 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.
::# 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]]''".
::# Same, but put it at the top of the Talk: page.
::# Make a page for listing which pages contain substantial amounts of material from what sources.
::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.

::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.

::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.

::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.

::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)

== Which emacswiki.org topics to work on? ==

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?

Does the site have any equivalents to MediaWiki's pages:

* [[Special:LongPages]]
* [[Special:MostLinkedPages]]
* [[Special:MostRevisions]]

? (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)

:If not, I wonder if search engines could help us approximate the "value" of each page?

:* https://www.google.com/search?q=site%3Aemacswiki.org

:Hmm. I'd take that as a no. Looks like a random selection. Any other ideas?

: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.

: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)
::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)

== Phone number spam ==

I've been seeing lots of spam, by bots creating new pages. I don't believe I have permissions to delete them, and I'm not sure where I could go to suggest they be deleted. So I'm putting them here:

* [[855 .447 ..2444.. phone number for Cox customer service (((New Hampshire))) Cox customer service 855 .447 ..2444.. customer service for Cox (((New York))) Cox phone number]]
* [[Quickbooks 1-888-300-9067 contact quickbooks support phone number1]]
* [[1-866-560-7666 QuickBooks Point of Sale support number]]
* [[Quickbooks 1-888-300-9067 Quickbooks software support phone number2]]
* [[(1855 447 2444) Pogo customer service number Pogo customer service number]]
* [[K A T A P P A!!!@!~!!(( 18555801808 )))!!~@ facebook helpline phone number facebook contact email telephone number for facebook]]
* [[Canada 1-888-300-9067 QuickBooks online phone number3]]
* [[Canada 1-888-300-9067 QuickBooks online phone number1]]
* [[1 844 405 0214 google support number google support phone number raftaar]]
* [[NIRMAND 18558554535$$ facebook customer service number facebook support phone number fvdshfvggpp]]

It seems like they are largely from July 2017. If I hit "random page", I get a spam page about 90% of the time, so I expect there are a whole lot of these pages.

[[User:Zck|Zck]] ([[User talk:Zck|talk]]) 22:17, 11 March 2025 (UTC)

=== spam: deleteBatch extension? ===

Hey Zck, indeed :( I'd like to mass-delete them.

I found this special page: https://wikemacs.org/wiki/Special:Nuke but it only looks for recent pages.

There might be another extension: https://www.mediawiki.org/wiki/Extension%3aDeleteBatch but it isn't install. We have to contact Jesse.

Or use an API? https://www.mediawiki.org/wiki/Manual:Pywikibot/login.py or another program, a browser automation tool?

[[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 12:34, 12 March 2025 (UTC)

Talk:Main Page

2025-03-12T12:34:40Z

Elvince: /* Phone number spam */

== IMPORTANT: Offline discussion ==

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

== IMPORTANT: Content Quality guidelines ==
I think before flame wars and fights among members, we should form
proper/strict guide lines for each aspect of the site. [http://depuypinnaclelawsuit.webnode.com/ DePuy Pinnacle Lawsuit] Wikipedia has very strict
rules about that., even their bots can tell the content quality of a
page. we can create articles in "WikEmacs" Namespace. [[User:Kindahero|Kindahero]] 23:57, 1 April 2012 (EEST)

: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)

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

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

== Markup Conventions==

=== Wikipedia linking convention ===

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

=== EmacsWiki linking convention ===

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

== Describing Modes and Packages ==

=== Naming Conventions ===

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

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

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

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

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

::::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)

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

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

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

== Syntax highlighting ==

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

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

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

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

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

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

: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)

== needed plugins ==

* 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.?

: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)

== WikEmacs staying open? Great! ==

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)

: 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)

:: 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)

== Keeping the licence situation clear and clean ==

Just noting the current situation...

* 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].
* The GNU Emacs manual is published under GFDLv1.3+
* Existing WikEmacs texts are under GFDLv1.3+

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]''".

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).

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.

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)

: 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)

::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.

::The two other issues are the copyright details, and the licence of original contributions.

::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>''".

::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.

::(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.)

::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:
::# 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.
::# 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]]''".
::# Same, but put it at the top of the Talk: page.
::# Make a page for listing which pages contain substantial amounts of material from what sources.
::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.

::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.

::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.

::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.

::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)

== Which emacswiki.org topics to work on? ==

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?

Does the site have any equivalents to MediaWiki's pages:

* [[Special:LongPages]]
* [[Special:MostLinkedPages]]
* [[Special:MostRevisions]]

? (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)

:If not, I wonder if search engines could help us approximate the "value" of each page?

:* https://www.google.com/search?q=site%3Aemacswiki.org

:Hmm. I'd take that as a no. Looks like a random selection. Any other ideas?

: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.

: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)
::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)

== Phone number spam ==

I've been seeing lots of spam, by bots creating new pages. I don't believe I have permissions to delete them, and I'm not sure where I could go to suggest they be deleted. So I'm putting them here:

* [[855 .447 ..2444.. phone number for Cox customer service (((New Hampshire))) Cox customer service 855 .447 ..2444.. customer service for Cox (((New York))) Cox phone number]]
* [[Quickbooks 1-888-300-9067 contact quickbooks support phone number1]]
* [[1-866-560-7666 QuickBooks Point of Sale support number]]
* [[Quickbooks 1-888-300-9067 Quickbooks software support phone number2]]
* [[(1855 447 2444) Pogo customer service number Pogo customer service number]]
* [[K A T A P P A!!!@!~!!(( 18555801808 )))!!~@ facebook helpline phone number facebook contact email telephone number for facebook]]
* [[Canada 1-888-300-9067 QuickBooks online phone number3]]
* [[Canada 1-888-300-9067 QuickBooks online phone number1]]
* [[1 844 405 0214 google support number google support phone number raftaar]]
* [[NIRMAND 18558554535$$ facebook customer service number facebook support phone number fvdshfvggpp]]

It seems like they are largely from July 2017. If I hit "random page", I get a spam page about 90% of the time, so I expect there are a whole lot of these pages.

[[User:Zck|Zck]] ([[User talk:Zck|talk]]) 22:17, 11 March 2025 (UTC)

=== spam: deleteBatch extension? ===

Hey Zck, indeed :( I'd like to mass-delete them.

I found this special page: https://wikemacs.org/wiki/Special:Nuke but it only looks for recent pages.

There might be another extension: https://www.mediawiki.org/wiki/Extension%3aDeleteBatch but it isn't install. We have to contact Jessy.

Or use an API? https://www.mediawiki.org/wiki/Manual:Pywikibot/login.py or another program, a browser automation tool?

[[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 12:34, 12 March 2025 (UTC)

GNU Emacs 30.1

2025-03-12T00:33:47Z

Elvince: Emacs 30.1

See:

* https://www.masteringemacs.org/article/whats-new-in-emacs-301
* https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-30

= What's new in Emacs 30.1 =

* completion-preview-mode: a replacement for company-mode
* native and faster JSON parser
* which-key mode is built-in
* native completion is on by default
* official Android support
* Tree Sitter improvements
* Emacs is now the default application for 'org-protocol'
* and more!

= How to get it =

== AppImage ==

Unofficial AppImage for latest releases:

* https://github.com/blahgeek/emacs-appimage

= How to build it =

<code>
sudo apt install build-essential autoconf automake texinfo libgtk-3-dev libxpm-dev libjpeg-dev libgif-dev libtiff-dev libgnutls28-dev libncurses-dev libjansson-dev libgccjit-10-dev ./configure –with-tree-sitter

(On Debian 12, get libgccjit-12-dev)

make -j16

sudo make install
</code>

Main Page

2025-03-12T00:24:11Z

Elvince: Emacs 30.1

'''WikEmacs''' is here to stay. Spread the word!

[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]
__NOTOC__
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.

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

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

* Priority tasks
** 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.
* Intermediate tasks
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].
** Add more content to [[Special:ShortPages|short pages]].
** Document or add more [[:Category:Third Party Package|third party packages]].
* Other tasks
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.
** Add more members to various [[Special:Categories|categories]].
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].
** 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).

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

The latest stable release of Emacs is [[GNU Emacs 30.1|Emacs-30.1]] released in February, 2025. The precedent is [[GNU Emacs 29|Emacs-29]].

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]].

<div style="float: left; width: 49%;">
== Explore WikEmacs ==

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

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

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

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

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

</div>

<div style="float: right; width: 49%;">

==Help build WikEmacs==

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.)



* [[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])
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])

[[Category:WikEmacs]]

Talk:Installing Emacs on GNU/Linux

2024-10-15T15:03:28Z

Elvince: install with guix, distrobox, other channels ?

Maybe we should add instructions about Emacs 23 as well? [[User:Bozhidar|Bozhidar]] 13:46, 28 March 2012 (EEST)

: This should be "installation emacs GNU/linux" or something instead of GNU/linux [[User:Kindahero|Kindahero]] 16:14, 29 March 2012 (EEST)

:: Good point. [[User:Bozhidar|Bozhidar]]

== Emacs-24 ==

I have XUbuntu 15.10 (Wily) and <code>sudo apt-get install emacs-24 emacs24-el emacs24-common</code> worked with the default repos, and installed 24.5.
The note about emacs-24 (using an unsupported repo; installing 24.3) looks obsolete. --[[User:David Biesack|David Biesack]] ([[User talk:David Biesack|talk]]) 10:26, 26 January 2016 (EST)

== Other installation channels ==

The introduction mentions them and it would be great to have details: how to install Emacs with Guix, Distrobox or unofficial package channels. [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 15:03, 15 October 2024 (UTC)

Media player

2024-08-18T07:07:41Z

Elvince: Ready player

What are the available media players for Emacs ?

= EMMS =

EMMS, The Emacs Multimedia System.

[https://www.gnu.org/software/emms/manual/ EMMS] is the Emacs Multimedia System. It tries to be a clean and small application to play multimedia files from Emacs using external players. Many of its ideas are derived from MpthreePlayer , but it tries to be more general and cleaner.

The fact that EMMS is based on external players makes it powerful, because it supports all formats that those players support, with no effort from your side.

== Features ==

* Audio support : MP3, Ogg Vorbis, FLAC
* Video support : MPEG, WMV, MOV, AVI, OGM, MKV, etc...
* Tagging capability, possibly batched
* Playlist management
* Remotely drivable via emacsclient (playlist creation via rox-filer, for example)
* covers display
* Dired integration
* interactive metadata browser
* synchronized lyrics display
* connection to GNU FM radio streams
* Extensible

[[File:emms-covers.png|600px|the emms multimedia player showing covers]]

== Installation ==

Install the needed packages with the package manager of your system :

<source lang="bash">
sudo apt-get install emms vorbis-tools
</source>

(you may also try with [http://wikemacs.org/wiki/El-get el-get].)

add the following to your ~/.emacs :

<source lang="scheme">
(require 'emms-setup)
(emms-all)
(emms-default-players)
</source>
and, as usual, restart emacs or ''M-x eval-current-buffer RET''.

== Usage ==

You can play a file or a directory with the command ''M-x emms-play-file'' or ''emms-play-directory''.

You can add files and directories to the emms playlist (which will be created if it doesn't exist yet) with ''M-x emms-add-file'', play it with emms-start and you can '''visit the playlist buffer''' by simply calling '''M-x emms RET'''. Hitting '?' in the playlist buffer will show you all the available shortcuts.

=== Add other file extensions ===

If you want to, say, be able to '''read flv videos''' :
<source lang="scheme">
;; add flv and ogv
(define-emms-simple-player mplayer '(file url)
(regexp-opt '(".ogg" ".mp3" ".wav" ".mpg" ".mpeg" ".wmv" ".wma"
".mov" ".avi" ".divx" ".ogm" ".asf" ".mkv" "http://" "mms://"
".rm" ".rmvb" ".mp4" ".flac" ".vob" ".m4a" ".flv" ".ogv" ".pls"))
"mplayer" "-slave" "-quiet" "-really-quiet" "-fullscreen")
</source>

== Extensions ==

=== Get lyrics of current song ===

We have to install '''emms-get-lyrics.el'''.

With [[el-get]] : '''el-get-install RET emms-get-lyrics RET'''.

Or :
* save https://raw.github.com/talau/elisp/master/emms-get-lyrics.el in your ~/.emacs.d/my-extensions
* be sure you have [[emacs-w3m]] installed
* add those two lines in your ~/.emacs :
<source lang="scheme">
(add-to-list 'load-path "~/.emacs.d/my-extensions/")
(require 'emms-get-lyrics)
</source>
* {{Command|evaluate-current-buffer}}

Then start playing a song and call {{Command|emms-get-lyrics-current-song}}.

Excerpt from its documentation :
<blockquote>
The function 'emms-get-lyrics-current-song' tries to get the lyrics
of the song that emms is currently playing [from http://www.lyricwiki.org/]. It currently requires
w3m to get the lyrics. It copies the lyrics to a file ending in
.lyrics; if the variable `emms-get-lyrics-use-files' is nil, it
will just display the lyrics in a buffer without saving them to a
file. If the variable `emms-get-lyrics-dir' is non-nil, then the
lyrics will be put in this directory with the file
ARTIST-TITLE.lyrics; otherwise it will be put in the same directory
as the song file, in a file with the same name as the song file
except the extension will by ".lyrics".
</blockquote>

== External links ==

The official documentation: https://www.gnu.org/software/emms/manual/

http://www.emacswiki.org/emacs/EMMS

http://www.gnewsense.org/Documentation/Emacs#Listening_to_Music an easy tutorial to begin with.

= Mpg123 =

'''mpg123''' is a package written by HiroseYuuji for playing .mp3 and .ogg files with the mpg123 and ogg123 programs. It can:

* play local music
* create and save playlists
* play randomly
* repeat songs
* loop inside songs

It is maybe the simplest player for Emacs you will find.

With extensions you can also:

* control the player from outside
* edit ID3 tags
* drag and drop music files from Dired

== Installation ==

=== package.el ===

'''mpg123.el''' is on [[MELPA]].

Its latest version (2023-05 at the time of writing) is for Emacs 28. You might experience a freeze of the interface in Emacs 27 when playing.

=== Debian system ===

You'd be better off using package.el, but you will also find a (historical) Debian package.

Install the [http://packages.debian.org/search?keywords=mpg123-el mpg123-el package] :

<source lang="bash">
apt-get install mpg123-el
</source>

restart emacs, and you can start using it.

=== Dependency for all systems ===

Install the mpg123 and ogg123 programs with your system's package manager :
<source lang="bash">
apt-get install mpg123 ogg123
</source>

=== Manual install ===

The sources are on [http://www.gentei.org/~yuuji/software/mpg123el/ mpg123.el's git repository]. You can save them in ''~/.emacs.d/mpg123.el''.

Check you have the following in your [[Init_File]] :

<source lang="scheme">
(add-to-list 'load-path "~/.emacs.d/")
</source>

restart emacs or {{Command|eval-current-buffer}}.

== Usage ==

{{Command|mpg123}}
: start mpg123, choose a directory or a mp3/ogg file and start listening. The buffer shows a complete list of commands.

<source lang="text">
1 --:--/--:-- Hurricane by Kyuss
0%--------------------------------------50%-------------------------------------100%
Volume: [N/A] Repeat: [--] Loop: [--]
mpg123:
W Show the real filename
g Go to current music line
SPC Play or pause
RET Play
m Mark position (when playing)
r Restart from marked position
w Where is the marked position
< <<
> >>
f Forward 1 sec
b Backward 1 sec
F Forward 10 sec
B Backard 10 sec
n Move to next line
p Move to previous line
g Go to current music line
- Volume down
+ Volume up
o Open other directory or playlist file
a Add other directory or playlist file
S Save current playlist to a file
i Increase repetition count
d Decrease repetition count (-1 for infinity)
L Increase current loop count
l Decrease current loop count. Also toggles between 0(no loop) and -1(always loop)
s Shuffle music list
D Delete music file
. Display playing position indicator
k Kill music line and push onto stack
y Yank music line from stack
I Intro-quiz mode ON/OFF (Stop at marked position)
q Quit
Q Quit without query
<down-mouse-2> Select a music directly on the mouse cursor
0..9 Digit argument (ex. 50V increase volume by 50steps)
----
The delimiter line "-------" is the indicator of currently playing position.
You may see the slider on the line running from left to right while the
music's going ahead. If you hit RET or <down-mouse-2> on the indicator line,
the music will immediately move to that position.
</source>

== Remote control ==

Save this file somewhere, like in .emacs.d/my-plugins:
http://www.gentei.org/~yuuji/software/mpg123el/mpg123-remote.el

add in your .emacs:
(load "path/to/mpg123-remote")

restart emacs. To control mpg123 from the outside, you have to start a server, for example with M-x server-start. Now you have access to a few functions that you can call this way:

emacsclient -e '(remote-mpg123-pause)' ; next and prev are also available

define a global shorcut with your desktop manager and you're done !

sources : http://www.gentei.org/~yuuji/software/mpg123el/

= Bongo =

Bongo is a beautiful, flexible and usable buffer-oriented media player for Emacs, developed in parallel to EMMS 2.0. If you store your music collection locally and use structured file names, then Bongo is a great way for you to play music from within Emacs.

Notable features of Bongo include :

* separate playlist and library buffers (each of which you may have any number — even zero of both is okay if you don’t need playlist functionality),
* hierarchical buffers with collapsable sections for each artist and album,
* familiar Emacs bindings for editing Bongo buffers (edit playlists much like you would regular text),
* a nice visual seeking interface doubling as a progress meter (hit ‘s’),
* a visual audio volume control (Volume, which is actually a stand-alone package),
* built-in support for playing and retreiving information about audio CDs,
* built-in support for submitting information to Last.fm using ‘lastfmsubmitd’,
* the ability to perform arbitrary actions (stopping playback is a simple example) once playback reaches certain points in the playlist, using so-called “action tracks”,
* an XMMS-like keymap for XMMS refugees,
* zero-configuration, out-of-the-box rock’n’roll action.

Bongo woks with many backend processes : mpg123, mplayer, vlc, ogg123, timidity and others.

An advantage of Bongo over EMMS may be that it can hook into Dired, so one would sort and manage files in Dired and press '''e''' to add a track to the playlist.

== Installation ==

There is no el-get recipe for bongo (is there for MELPA in emacs24 ?). You have to install it from git. It is a 3 steps process :

* go to where you want to put the sources :
<source lang="bash">
cd ~/.emacs.d/your-extensions
</source>

* retrieve the sources :
<source lang="bash">
git clone git://github.com/dbrock/bongo.git
</source>

* Add the Bongo directory to your ‘load-path’, and then run {{Command|load-library RET bongo RET}}. Here’s what you’ll want to put in your ~/.emacs:
<source lang="scheme">
;; Change this to the correct directory name for you.
(add-to-list 'load-path "~/.emacs/your-extensions/bongo")
(autoload 'bongo "bongo"
"Start Bongo by switching to a Bongo buffer." t)
</source>

== Usage ==

Run Bongo with (have a guess) {{Command|bongo}} and you'll be left with a quite explicit buffer. To learn more commands, please notice the menu entry and see the documentation at the project's page.

<source lang="text">

[here a nice Bongo logo]

Welcome to Bongo, the buffer-oriented media player!

This is a Bongo library buffer. It's empty now, but in a
few moments it could hold your entire media collection ---
or just the parts that you are currently interested in.

To insert local media files or directories, use `i'.
To insert the URL of a media file or stream, use `I u RET'.
To insert other things, use `I TAB' to list possibilities.

To enqueue tracks in the nearest playlist buffer, use `e'.
To hop to the nearest playlist buffer, use `h'.

Enabled backends: mpg123, mplayer, ogg123
To modify this list, customize `bongo-enabled-backends'.

Bongo is free software licensed under the GNU GPL.
Report bugs to <bongo-devel@nongnu.org>.

</source>

Basically, you're going to switch between a '''library buffer''' and a '''playlist buffer'''. You have to add tracks to the library, as indicated. Then you can start playing a track (enter). This adds the track on the playlist buffer. You can switch between buffers with '''h'''.

When on the library buffer, to add a track to the end of the playlist, press '''e'''. To add it at the beginning, press '''E'''.

* Pause playback : SPC
* Stop playback : '''C-c C-s'''

== Getting further ==

Check the good documentation on the project's page :
https://github.com/dbrock/bongo

== Play radio ==

Bongo can read online streams out of the box. As said in the buffer, press '''i''' and paste your stream's url.

== Remote control ==

Use '''bongo-pause/resume''', '''bongo-next''' and '''bongo-previous''' and couple them with [http://wikemacs.org/wiki/Emacs_server EmacsServer].

<source lang="scheme">
emacsclient -e '(bongo-pause/resume)'
</source>

== Issues ==

=== Can't play tracks continuously ===

If Bongo plays a track and stops, try only enabling the mplayer backend only:

(setq-default bongo-enabled-backends '(mplayer))

== External links ==

Official site : https://github.com/dbrock/bongo
Some hacks : http://www.emacswiki.org/emacs/BongoHacks (edit tags, add files from dired,…)

= mpdel, a client to MPD =

[https://github.com/mpdel/mpdel/tree/e09904bf31ed465ea93ef2c165e8a6f705229f57 MPDel] is an emacs client for the Music Player Daemon. MPDel provides an Emacs user interface to control playback (play, pause, next, volume up…) and to display and control the current playlist as well as your stored playlists (e.g., “my favorites”, “wake me up”, “make me dance”, …).

= Dionysos music player=

[https://github.com/nlamirault/dionysos Dionysos] (in melpa) is a music player which accepts as backends mpv, mpd and vlc.

= Vuiet =

[https://github.com/mihaiolteanu/vuiet Vuiet] is a music player and explorer, with recommendations based on Lastfm or Spotify. It can:

* search songs and artists
* create playlists, including '''smart playlists''' which play songs indefinitely based on criteria
* explore artists and genres with Lastfm
* search tracks on '''youtube''' and play them with mpv
* display and save '''lyrics'''
* search inside the saved lyrics

= Listen =

[https://github.com/alphapapa/listen.el Listen.el] is a minimalist music player.

Requires: Emacs 29.1.

= ready-player =

[https://github.com/xenodium/ready-player/ ready-player] is a lightweight major mode to open media (audio/video) files in an Emacs buffer.

By default, ready-player-mode will try to use either mpv, vlc, ffplay, or mplayer.

[[File:Ready-player.png|thumb]]

[[Category:Entertainment]]

File:Ready-player.png

2024-08-18T07:05:09Z

Elvince:

User talk:Jlquinn

2024-08-15T14:58:00Z

Elvince: hello new user

Hello and welcome! Any pages you want to take care of? [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 14:58, 15 August 2024 (UTC)

Imenu

2024-07-04T00:45:22Z

Elvince: /* Customisation */ add to menu bar

{{Package
|name=Imenu
|description=https://www.gnu.org/software/emacs/manual/html_node/elisp/Imenu.html
|author=
|source=
|in_emacs=yes
|Development status=active
}}

'''Imenu''' produces menus for accessing locations in documents, typically in the current buffer. You can access the locations using an ordinary menu (menu bar or other) or using '''minibuffer completion'''.
'''
A typical use of Imenu shows a menu-bar menu that is an index or table of contents for the current buffer. For a source-code buffer it is typical to '''index definitions of functions, variables''', and so on.

You can use Imenu with any major mode and any programming language or document type. If there is no Imenu support for your context, you can add it using EmacsLisp and the constructs provided in library 'imenu.el'.

Library imenu+.el ([[Imenu+]]) extends standard library imenu.el.

= Customisation =

== Add an entry menu ==

You can add the imenu listing in the main menu bar. You have to add a hook to each mode:

<source lang="lisp">
(add-hook 'markdown-mode-hook #'imenu-add-menubar-index)
(add-hook 'makefile-mode-hook #'imenu-add-menubar-index)
(add-hook 'prog-mode-hook #'imenu-add-menubar-index)
</source>

The third line about prog-mode-hook adds imenu for all programming languages modes.

However, by default, changes to the file will not automatically update the index menu. Set imenu-auto-rescan to t in local fashion as shown below:

<source lang="lisp">
(add-hook 'markdown-mode-hook (lambda () (setq-local imenu-auto-rescan t)))
(add-hook 'makefile-mode-hook (lambda () (setq-local imenu-auto-rescan t)))
(add-hook 'prog-mode-hook
(lambda ()
(setq-local imenu-auto-rescan t)
(setq-local imenu-sort-function #'imenu--sort-by-name)))
</source>

== Add an entry to the context menu ==

<source lang="lisp">
(add-hook 'prog-mode-hook 'context-menu-mode)
</source>

== Using ido ==

Using [[ido]] in conjunction with imenu makes it very easy and quick to use. Add the following function into your ~/.emacs :

<source lang="scheme">
(defun ido-goto-symbol (&optional symbol-list)
"Refresh imenu and jump to a place in the buffer using Ido."
(interactive)
(unless (featurep 'imenu)
(require 'imenu nil t))
(cond
((not symbol-list)
(let ((ido-mode ido-mode)
(ido-enable-flex-matching
(if (boundp 'ido-enable-flex-matching)
ido-enable-flex-matching t))
name-and-pos symbol-names position)
(unless ido-mode
(ido-mode 1)
(setq ido-enable-flex-matching t))
(while (progn
(imenu--cleanup)
(setq imenu--index-alist nil)
(ido-goto-symbol (imenu--make-index-alist))
(setq selected-symbol
(ido-completing-read "Symbol? " symbol-names))
(string= (car imenu--rescan-item) selected-symbol)))
(unless (and (boundp 'mark-active) mark-active)
(push-mark nil t nil))
(setq position (cdr (assoc selected-symbol name-and-pos)))
(cond
((overlayp position)
(goto-char (overlay-start position)))
(t
(goto-char position)))))
((listp symbol-list)
(dolist (symbol symbol-list)
(let (name position)
(cond
((and (listp symbol) (imenu--subalist-p symbol))
(ido-goto-symbol symbol))
((listp symbol)
(setq name (car symbol))
(setq position (cdr symbol)))
((stringp symbol)
(setq name symbol)
(setq position
(get-text-property 1 'org-imenu-marker symbol))))
(unless (or (null position) (null name)
(string= (car imenu--rescan-item) name))
(add-to-list 'symbol-names name)
(add-to-list 'name-and-pos (cons name position))))))))

(global-set-key (kbd "C-c i") 'ido-goto-symbol) ; or any key you see fit
</source>

Now, '''M-x eval-current-buffer''', hit '''C-c i''' and enjoy quick navigation through your code.

== imenu-list: show the menu list in a thin sidebar buffer ==

[https://github.com/bmag/imenu-list imenu-list] is a plugin (in melpa) to show the current buffer's imenu entries in a separate (and thin) buffer.

[[File:imenu-list-light.png]]

== imenu-anywhere: get a menu list across several buffers ==

[https://github.com/vspinu/imenu-anywhere imenu-anywhere] (on [[MELPA]] and MELPA stable) allows to construct the menu list by looking into several buffers. By default it looks into buffers of the same mode, the same project and "friendly modes" (defined in <code>imenu-anywhere-friendly-modes</code>).

To bind it to a key of your choice do something like:

<source lang="lisp">
(global-set-key (kbd "C-.") #'imenu-anywhere)
</source>

= See also =

== helm-imenu ==

[[Helm]] is a nice package that provides interactivity for lots of commands. Here '''helm-imenu''' (provided by the helm package) offers to interactively select a variable declaration, a method, a class (or something else depending on the language support).

[[File:helm-imenu.gif]]

== ace-jump, quick cursor movements ==

[[ace-jump]], for quick and direct cursor movement on current view.

[[Category:Intermediate]]
[[Category:Navigation]]
[[Category:Buffer Navigation]]

Python

2024-06-25T14:40:15Z

Elvince: /* Virtual environments */ add emacs-pet

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.

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.

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.

See also [[Django]] support.

== Default modes ==

There are a number of python modes for Emacs.
fgallina's [https://github.com/fgallina/python.el python.el] is the python.el included in Emacs 24.2 and onwards.

== All-in-one solutions ==

=== emacs-for-python ===

'''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.

[https://github.com/gabrielelanaro/emacs-for-python/ emacs-for-python at github]

=== Elpy ===

'''Elpy''' is a collection of elisp packages for Python too.

https://github.com/jorgenschaefer/elpy/wiki/Features

It permits, among others, to:

* refactor code (using rope),
* send a region or a buffer to a python interpreter,
* run unit tests, run the test the cursor is in, with a test runner of choice (django, pytest, …),
* jump to a symbol definition (elpy-goto-definition),…

and of course

* on-the-fly checks with flymake,
* code completion with company-mode and either rope or jedi,
* on the fly code helper with eldoc (and rope or jedi),
* code navigation,
* change of virtual environment inside Emacs (pyvenv), etc

=== EMP: EMacs Python ===

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.

https://kootenpv.github.io/2016-01-01-emacs-python

=== Emacs-bootstrap ===

[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.

== Language Server Protocol support ==

See [https://github.com/joaotavora/eglot eglot], a polyglot LSP mode for Emacs (by the author of Yasnippet,…),

and [https://github.com/palantir/python-language-server pyls] specifically for Python.

== Refactoring ==

=== rope & ropemacs ===

==== Presentation ====

'''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.

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.

But Rope can do more than this simple example, it can:

* Rename anything
* Extract method/local variable
* Change method signature
* Perform cross-project refactorings
* Support Mercurial, GIT, Darcs and SVN in refactorings

Rope can also help IDE's with:

* Auto-completion
* Finding definition location
* Getting pydoc
* Finding occurrences
* Organizing imports (removing unused and duplicate imports and sorting them)
* Generating python elements

==== Installation ====

Note: see also emacs-traad below that has an easy installation process.

===== With el-get =====

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.

===== Manually =====

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 .

sudo pip install rope ropemacs

As of February 2014 you can't install Pymacs via pip, therefore:

git clone http://github.com/pinard/pymacs
cd pymacs
make check
sudo make install

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.

'''After you do the make install of pymacs do not delete the folder.Copy the file pymacs.el to ~/.emacs.d/site-lisp/'''

Now add path of pyamcs.el to your ~/.emacs file,using this code:
(setq emacs-config-path "~/.emacs.d/")
(setq base-lisp-path "~/.emacs.d/site-lisp/")
(setq site-lisp-path (concat emacs-config-path "/site-lisp"))
(defun add-path (p)
(add-to-list 'load-path (concat base-lisp-path p)))
(add-path "")
(add-to-list 'load-path "~/.emacs.d")

You can now lazily load ropemacs or load it at runtime.For lazy evaluation add this to your .emacs file:
(defun load-ropemacs ()
"Load pymacs and ropemacs"
(interactive)
(require 'pymacs)
(pymacs-load "ropemacs" "rope-")
;; Automatically save project python buffers before refactorings
(setq ropemacs-confirm-saving 'nil)
)
(global-set-key "\C-xpl" 'load-ropemacs)

use c-xpl to load ropemacs.Read more about it [https://github.com/python-rope/ropemacs#setting-up here]

=== Rope & traad ===

[https://github.com/abingham/traad Traad] is a client-server approach to using the rope Python refactory library. It involves two basic components:
* A HTTP server exposing the rope API via JSON, and
* Client libraries for talking to the server
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.

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.

==== emacs-traad, easy installation and use ====

[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.

==== usage ====

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.

=== Other Python "refactoring" tools ===

==== Projectile - replace in project ====

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.

==== Iedit - replace occurences of a symbol ====

[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.

==== Red4e - change the method signature, add decorators ====

[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:

* '''add a decorator''', remove one, automatically adding or removing "self" for a staticmethod,
* '''add an argument''' (and rename it inside the method body), remove an argument, add the couple "*args, **kwargs",
* '''rename/copy/comment/kill the current method''' (and rename it in the project too),
* quickly go to another method (with imenu),
* toggle arguments on '''one or multiple lines''',
* and more, to be continued.

It uses under the hood (mostly, not everywhere) the redbaron python library that allows to manipulate an FST (Full Syntax Tree).

==== Pygen - code generation ====

See [https://github.com/JackCrawley/pygen pygen]. Unmaintained.

=== Refactor with Elpy ===

See Elpy's documentation: http://elpy.readthedocs.io/en/latest/ide.html?highlight=django#refactoring

One can refactor code (with rope), format code, edit all the occurences of the symbol at point simultaneously, and fix imports.

== Auto-Completion ==

=== Jedi ===

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.

Jedi is simple to install and it works out of the box.

See screenshots and get the full documentation : http://tkf.github.io/emacs-jedi/released/

Jedi's official page: http://jedi.jedidjah.ch/en/latest/

==== Installation ====

Install Jedi.el via el-get, Marmalade or MELPA (see install for more info) and add this to your Emacs configuration:
(add-hook 'python-mode-hook 'jedi:setup)
(setq jedi:setup-keys t) ; optional
(setq jedi:complete-on-dot t) ; optional

or call M-x jedi:setup

''Note'': it's nice to use it in a python interpreter inside emacs :)

=== Anaconda ===

'''Anaconda-mode''' is a mode for '''code navigation, documentation lookup''' and '''completion''' for Python.

It runs on '''emacs 24.3''' with python >= 2.6.

It provides:

* context-sensitive code completion for Python
* jump to definition
* find references
* view documentation
* virtualenv management

The package is available in [[MELPA]]. For more information, [https://github.com/proofit404/anaconda-mode read its documentation].

== Code Checker ==

=== Flymake and Flycheck ===

[[Flymake]] (in Emacs) is a on-the-fly syntax checker for Emacs.
We can use it with [[flycheck]] (in melpa), that aims at being a replacement.

To run pep8, pylint, pyflakes and unit-tests (with nose), you can be interested in using [https://github.com/akaihola/flymake-python flymake-python].

Don't forget about '''pylint''' too.

[[File:flycheck-annotated.png]]

=== MyPy checks ===

With [https://github.com/SerialDev/mypy-mode mypy-mode] we get a compilation-mode based support for python 3.6+ type hints checks.

As a side note, we can also get flycheck to work, at the same time as pylint, with:

<source lang="elisp">
(flycheck-define-checker
python-mypy ""
:command ("mypy"
"--ignore-missing-imports"
"--python-version" "3.6"
source-original)
:error-patterns
((error line-start (file-name) ":" line ": error:" (message) line-end))
:modes python-mode)

(add-to-list 'flycheck-checkers 'python-mypy t)
(flycheck-add-next-checker 'python-pylint 'python-mypy t)
</source>

== Indexing sources: ctags, cscope, pycscope ==

Indexing sources allows you to do neat things, like going to the definition of a function or finding which functions are calling another one.

Note that Elpy does the "go to definition" feature (elpy-goto-definition), without the need of indexing sources.

=== etags, ctags ===

'''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'''.

The primary use for the tags files is looking up class/method/function/constant/etc declaration/definitions. Cscope is more powerful (see below).

==== usage ====

Generate the tags with this command at the root of your project:

find . -name "*.py" -print | etags -

it creates the file TAGS.

Note that projects like [[Projectile]] or [[Helm]] provide an integrated use of etags (finding one, re-generating the index, etc).

=== cscope ===

'''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).

It was originally designed for C and C++, but thanks to version 0.3 of '''pycscope''', pythonistas can make use of it.

==== usage ====

The following commands should get you running:

apt-get install cscope
pip install pycscope
# in project base dir:
find . -name '*.py' > cscope.files
cscope -R

now install the '''xcscope''' emacs package with [[ELPA]] and require it:
(require 'xcscope)

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.

==== Interactivity with helm-cscope ====

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.

== Running tests ==

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

If you wish to modify the way it runs test, set the following variable:

<source lang="lisp">
(setq elpy-test-<django, nose, pytest>-runner-command '("./manage.py" "test"))
</source>

=== A Hydra to choose what tests to run, navigate errors and switch to the console ===

See this snippet: https://github.com/abo-abo/hydra/wiki/Elpy

=== Running Make, with completion of commands ===

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.

[[File:Make-helm.png]]

== Debugging ==

Well, let's start with the debuggers documentation:

* [https://docs.python.org/3/library/pdb.html pdb doc]
* [https://pypi.python.org/pypi/pdbpp/ pdb++] has a few more commands
* [https://pypi.python.org/pypi/ipdb ipdb] to make use of ipython (aka jupyter)

=== Ipdb, ipython debugger ===

If you call ipdb, the execution will stop and give a nice ipython-looking prompt.
Just add the line

import ipdb; ipdb.set_trace()

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.

Note: if you like IPython/Jupyter, look at the [https://github.com/millejoh/emacs-ipython-notebook Emacs IPython Notebook].

Note: You can use [[yasnippet]] to quickly enter this sentence, or just a simple function:

<source lang="lisp">
(defun python-add-breakpoint ()
"Add a break point"
(interactive)
(newline-and-indent)
(insert "import ipdb; ipdb.set_trace()")
(highlight-lines-matching-regexp "^[ ]*import ipdb; ipdb.set_trace()"))
</source>

You can use the following to highlight this line, and not forget it :
<source lang="scheme">
; Highlight the call to ipdb
; src http://pedrokroger.com/2010/07/configuring-emacs-as-a-python-ide-2/
(defun annotate-pdb ()
(interactive)
(highlight-lines-matching-regexp "import ipdb")
(highlight-lines-matching-regexp "ipdb.set_trace()"))
(add-hook 'python-mode-hook 'annotate-pdb)
</source>

And just delete every breakpoints of the buffer:
<source lang="list">
(defun ipdb-cleanup ()
(interactive)
(save-excursion
(replace-regexp ".*ipdb.set_trace().*\n" "" nil (point-min) (point-max))
;; (save-buffer)
))
</source>

=== pdb track ===

If you use emacs-for-python given above, you can track your source code while debugging with pdbtrack.

A tool to use in a non-emacs terminal would be [https://pypi.python.org/pypi/pdbpp/ pdbpp]

=== Realgud, a front end to many debuggers to stay in the source window ===

[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.

[[File:Realgud.png]]

=== Redefine the code being run in the debugger session ===

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).

=== M-x compile and breakpoints ===

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:

<source lang="lisp">
; thanks to https://masteringemacs.org/article/compiling-running-scripts-emacs (slightly modified)
(defadvice compile
(before ad-compile-smart activate)
"Advises `compile' so it sets the argument COMINT to t if breakpoints are present in `python-mode' files"
(when (derived-mode-p major-mode 'python-mode)
(save-excursion
(save-match-data (goto-char (point-min))
(if (search-forward "ipdb.set_trace()"
(point-max)
t)
(progn (ad-set-arg 1 t)
(switch-to-buffer-other-window "*compilation*")))))))
</source>
Now just run '''M-x compile''' as usual.

=== Debug Adapter Protocol - dap-mode, LSP for debugging ===

[https://emacs-lsp.github.io/dap-mode/ dap-mode] is a client/library for [https://microsoft.github.io/debug-adapter-protocol/ Debug Adapter Protocol], a wire protocol for communication between client and Debug Server. It's similar to the LSP but provides integration with debug server.

You can set breakpoints in your code, step, evaluate statements, launch or attach to debugging sessions, etc. You can use '''dap-hydra''' to see the available actions.

== Documentation ==

=== Choose your docstring fill-paragraph style (M-q) ===

If you call '''M-q''' (fill-paragraph) inside a Python docstring, Python-mode will format it following PEP-257: the first sentence is on the same line with the opening quotes and a blank line is inserted before the closing quotes, like so:

<source>
def foo():
"""My docstring.

"""
pass
</source>

Perhaps you prefer the Django style:

<source>
def foo():
"""
My docstring.
"""
pass
</source>

To make '''M-q''' respect the Django style, use this setting:

(setq python-fill-docstring-style 'django)

=== Insert Sphinx docstrings ===

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.

=== Eldoc: argument list in the echo area ===

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'''.

To always enable it:

(add-hook 'python-mode-hook 'eldoc-mode)

=== Jedi: show the method signature, show documentation ===

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'''.

There is also '''M-x jedi:show-doc''' to show the docstring for the symbol at point in another window.

See more in [https://jedi.readthedocs.io/en/latest/ the Jedi documentation].

=== helm-pydoc ===

'''helm-pydoc''' is a little utility that lets you interactively select a module you want read the doc and displays it in another buffer.

=== pydoc linkification ===

If you've ever used the emacs lisp documentation system, you may find that the pydoc is poorer in functionnalities:
* there is no direct link to code source
* there is no "back" button

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].

=== info format ===

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].

== Datascience ==

=== the Scimax starter kit ===

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.

=== Ipython / Jupyter notebooks ===

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] !

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].

[[File:emacs-ipython.png||||the emacs ipython notebook, mixing and evaluating code, text and graphics]]

=== lpy - eval a region, step through expressions ===

[https://github.com/abo-abo/lpy lpy] is a little tool that offers to:

* press '''e''' in the right position (before an expression) to eval it,
* press '''j''' to go to the next expression

and more ! It's a new tool in development (by a great developer, rest assured the doc will follow ! :p)

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]
for Python. Unfortunately,
Python isn't nearly as well-structured as LISP. But Python is
ubiquitous, and the less powerful `lpy-mode' is better than nothing
at all. The basic idea of `lpy-mode' is to increase the editing efficiency
by binding useful navigation, refactoring and evaluation commands
to unprefixed keys, e.g. "j" or "e". But only in certain point
positions, so that you are still able to use uprefixed keys to
insert themselves.
Example, here "|" represents the point position:

print |("2+2=%d" % (2 + 2))

Here, if you press the key "e", the whole line will be evaluated
and "2+2=4" will be printed in the Echo Area.

=== Send the current paragraph to the REPL, go to the next paragraph ===

<source lang="elisp">
(defun my-python-para-send-and-step ()
"Sends the current paragraph to the python REPL and goes to the next one"
(interactive)
(mark-paragraph)
(python-shell-send-region)
(forward-paragraph))
</source>

=== Send code to the REPL (isend-mode, eval-in-repl) ===

This is actually a default feature of python.el. See its menu to send a line or a region to the repl.

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'''.

=== See also ===

* [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.

== Other tools ==

=== Virtual environments ===

Some tools allow to apply the changes of virtual environment activation inside emacs. They make '''M-x compile''' aware of the environment, etc.

* [https://github.com/wyuenho/emacs-pet pet] should supersede the other solutions. I tracks down the correct Python tooling executables from your virtualenvs so you can glue the binaries to Emacs, without configuration.
* «The first time you call one the few pet helper functions, it will use Projectile or project.el to detect the root of your project, search for the configuration files for the many supported Python virtualenv tools, and then lookup the location of the virtualenv based on the content of the configuration files. Once a virtualenv is found, all executables are found by looking into its bin directory.»

* [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.

* [https://github.com/jorgenschaefer/pyvenv pyvenv] sets the python path, uses virtualwrapper's hooks, ...

=== Python versions (pyenv) ===

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].

Once it's installed, we just have to switch with '''M-x pyenv-mode-set'''.

=== Pymacs ===

'''{{ModeLink|Pymacs}}''' is an Emacs extension that enables the use of Python alongside with Emacs Lisp.

[http://pymacs.progiciels-bpi.ca/index.html Pymacs homepage]

=== include import statements or remove unused ===

[[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

rmtree

and then execute {{Command|rope-auto-import}},

from shutil import rmtree

is inserted at the top of the file.

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'').

'''emacs-traad''' (see above) has a function '''traad-auto-import'''.

[https://github.com/Wilfred/pyimport pyimport] can add import statements or remove the unused ones (with pyflakes).

[http://elpy.readthedocs.io/en/latest/ide.html?highlight=django#refactoring Elpy] too can import missing ones.

See also [https://gitlab.com/emacs-stuff/python-import-add/ a snippet] to add many imports at once.

=== Sort import statements ===

See the '''py-isort''' [[Melpa]] package to automatically sort import statements.

=== pip-requirements mode ===

[http://melpa.org/#/pip-requirements pip-requirements] (in MELPA) is a major mode for editing pip requirements files, with the following features:
* syntax highlighting
* Auto completion of package names from PyPI
* togglable comments

=== pip utilities ===

[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.

[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:

* choose one requirements file of the project if many and install its packages,
* chooses the right virtual env,
* install a new package and add it into a requirements file (with interactive choice, needed when there is a "dev-requirements" for instance),
* check the current package version (with pip freeze),
* open the package page on pypi.

=== Code coverage with Python 3 ===

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]].

== Libraries ==

Let's put them on [[Python libraries]]. Hints to write Emacs packages for Python projects.

== Screencasts ==

These videos are of particular interest for Python development in Emacs:

* [https://www.youtube.com/watch?v=JmmTUIahB1U Emacs, Pyright and Eglot make for an excellent Python IDE]

== See also ==

You'll be certainly interested in the following packages (that you will find on [[ELPA]] or MELPA):

=== '''Magit''', a git interface ===

Emacs + git is magic : see [[magit]]

=== Code navigation: jump to function definitions ===

Get started with [[imenu]] and '''helm-imenu''' (see [[helm]]).

Then for cross-project code navigation see xcscope that answers questions like "show all methods that call this one".

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.

=== Code navigation: move by indentation levels ===

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.

[[File:indent-tools.gif]]

=== '''Yasnippet''', a template system ===

[[yasnippet]]

=== '''helm-pydoc''' to browse the documentation of installed packages and import one ===

=== '''pungi''' to integrate jedi, virtualenv and buildout ===

=== How to do code folding ===

See [[folding]]

=== other '''ELPA packages''' ===

If you're running Emacs with package support (usually Emacs 24 and later), check out what is available in [[ELPA]]:
; {{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.

[[Category:Programming languages]]
[[Category:Programming]]
[[Category:Python]]

User talk:Jbalint

2024-06-21T23:52:59Z

Elvince: Created page with "Hello and welcome! ~~~~"

Hello and welcome! [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 23:52, 21 June 2024 (UTC)

User talk:Bltejerina

2024-04-02T10:44:32Z

Elvince: hello new user

Welcome! [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 10:44, 2 April 2024 (UTC)

Buffer management

2024-03-07T20:23:00Z

Elvince: /* Ibuffer */ ibuffer-vc !

Let's list the possible ways to manage buffers. How to manage a lot of buffers, to get fuzzy completion, to work in distinct projects, workspaces, etc ?

What is a buffer exactly ? Check the [http://wikemacs.org/wiki/Emacs_Terminology#Buffer Emacs term].

= List current buffers =

== Ibuffer ==

Ibuffer is built-in. Nice extension: [https://github.com/abo-abo/hydra/wiki/Ibuffer hydra-ibuffer] will offer a nice prompt with ibuffer commands.

[[File:hydra-ibuffer.png]]

Another extension, [https://github.com/purcell/ibuffer-vc/ ibuffer-vc], allows to group the buffers by project directory (or more precisely, by the project root when they are under version conrol).

== Switch buffers with completion ==

Choose your favorite option: [[ido]], [[ivy]] or [[helm]].

= Work in projects =

== Projectile ==

In [[Projectile]], a project root is defined either by a source control repository either by a <code>.projectile</code> file. Among other features, it allows to show the list of buffers that belong to the current project and switch to it. It is by default bound to '''C-c p b''' ('''M-x projectile-switch-buffer'''). See also the menu. You can choose the completion engine for Projectile (helm, …).

= Work in distinct workspaces / perspectives =

== persp-mode ==

[https://github.com/Bad-ptr/persp-mode.el persp-mode] (in MELPA) implements named perspectives, i.e. a set of buffers/window configs, or also tagged workspaces. It is based on [https://github.com/nex3/perspective-el perspective-el] and adds the ability to share perspectives among frames and to save/restore its state from/to a file.

Once we activate the mode ('''M-x persp-mode''') we can carry on our work. Then we can create another group/perspective/workspace ('''persp-switch''' and entering a new name, '''C-x x s''' by default). Once we are in a new persp, the usual commands that list buffers will only list buffers from that one, not from the other perspectives.

== persp-projectile ==

[https://github.com/bbatsov/persp-projectile persp-projectile] (in MELPA) is a minor mode that provides the ability to manage different workspaces. If you need to open many projects at the same time, perspective can help you keep each project related buffers and windows setting separate from other projects, similar to multiple spaces on MacOS, which allows you to focus on the files of the current active project.

It is based on '''perspective-el''' listed above.

= Tabs =

Tabs may be a concept that do not translate very well in Emacs. We often advise to loose this habit and embrace the Emacs way (i.e., everything else listed in that page !). But you can emulate some tabs features of course.

== elscreen ==

[[elscreen]] (in MELPA) is a tabbed window session manager modeled after GNU screen. We can create tabs manually. With extensions, we can choose to isolate a tab's buffers from the others.

= Evil-mode, or switching buffers à la Vim =

That's possible with [[evil]]. Just do <code>:ls</code> and voilà :)

= See also =

== Keep a certain kind of buffers in a window: Purpose ==

[https://github.com/bmag/emacs-purpose emacs-purpose] ("window-purpose" on MELPA) provides a new window management system for Emacs, which gives you a better control over where Emacs displays buffers.

With Purpose, each buffer has a configurable "purpose" and each window can interactively be dedicated to a certain "purpose". When you dedicate a window (C-c , d), Purpose makes sure that this window will be used only for buffers which have the same purpose as the buffer that is currently displayed in that window.

== Frames only mode, better fit with tiling window managers ==

[https://github.com/davidshepherd7/frames-only-mode frames-only-mode] makes emacs play nicely with tiling window managers by setting it up to use frames rather than windows.

== Buffer navigation (Category) ==

[http://wikemacs.org/wiki/Category:Buffer_Navigation Buffer Navigation]

== Session Management ==

[[Session_management]]

[[Category:Buffer Management]]
[[Category:Buffers]]
[[Category:Third Party Package]]
[[Category:Workflow]]
[[Category:Intermediate]]

Notmuch

2024-02-24T22:04:35Z

Elvince: create notmuch mail page

{{Package
|name=notmuch
|description=Email client
|author=
|maintainer=
|screenshots=https://notmuchmail.org/screenshots/
|manual=http://https://notmuchmail.org/notmuch-emacs/
|source=https://git.notmuchmail.org/git/notmuch
|in_emacs=no
|Development status=active
|website=https://notmuchmail.org/
}}

[https://notmuchmail.org/ notmuch] is a "fast, global-search and tag-based email system to use within your text editor or in a terminal" that comes with an Emacs interface.

[[File:Notmuch-tree-split.png]]

[[Category:Third Party Package]]
[[Category:Email]]
[[Category:MUA]]
[[Category:Mail Client]]

File:Notmuch-tree-split.png

2024-02-24T22:01:21Z

Elvince: Notmuch Emacs interface, split tree view.

== Summary ==
Notmuch Emacs interface, split tree view.

2024-02-22T09:22:48Z

Elvince:

See:

* https://www.masteringemacs.org/article/whats-new-in-emacs-29-1
* https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29

= What's new in Emacs 29 =

Emacs 29.1 has a wide variety of new features, including:

* Official tree-sitter support
* EGlot, the Language Server Client, is now built-in
* Use-package is built-in
* Better long line support
* Native SQLite Support
* Changing the init directory (now possible)
* Pixel Scroll Precision Mode to get smooth scrolling

= How to get it =

== AppImage ==

Unofficial AppImage for latest releases:

* https://github.com/blahgeek/emacs-appimage

= How to build it =

<code>
sudo apt install build-essential autoconf automake texinfo libgtk-3-dev libxpm-dev libjpeg-dev libgif-dev libtiff-dev libgnutls28-dev libncurses-dev libjansson-dev libgccjit-10-dev ./configure –with-tree-sitter

# On Debian 12, get libgccjit-12-dev

make -j16

sudo make install
</code>

GNU Emacs 29

2024-02-22T09:21:17Z

Elvince: appImage, build it

GNU Emacs 29

2024-02-22T09:18:37Z

Elvince: Created page with "See: * https://www.masteringemacs.org/article/whats-new-in-emacs-29-1 * https://git.savannah.gnu.org/cgit/emacs.git/tree/etc/NEWS?h=emacs-29 = What's new in Emacs 29 = Emac..."

Main Page

2024-02-22T09:15:11Z

Elvince: Emacs 29.1

'''WikEmacs''' is here to stay. Spread the word!

[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]
__NOTOC__
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.

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

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

* Priority tasks
** 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.
* Intermediate tasks
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].
** Add more content to [[Special:ShortPages|short pages]].
** Document or add more [[:Category:Third Party Package|third party packages]].
* Other tasks
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.
** Add more members to various [[Special:Categories|categories]].
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].
** 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).

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

The latest stable release of Emacs is [[GNU Emacs 29|Emacs-29.1]] released on July 30th, 2023. The precedent is [[GNU Emacs 28|Emacs-28.1]].

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]].

<div style="float: left; width: 49%;">
== Explore WikEmacs ==

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

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

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

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

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

</div>

<div style="float: right; width: 49%;">

==Help build WikEmacs==

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.)



* [[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])
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])

[[Category:WikEmacs]]

2022-07-01T08:02:52Z

Elvince: /* Mpg123 */ is broken on Emacs 27 :( so long.

User talk:Ray Kuo

2022-04-21T22:02:07Z

Elvince: hello

Hello new Wikemacs user! We are are not a big tribe here, but we're nice. You can watch the RSS feed to watch all changes to the site.
Is there something specific you wanted to do?
I think Wikemacs is great for tutorials (see the Elisp ones) and pages that sum up a lot of stuff (Git, Python, Dired…).
See you around o/ [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 18:02, 21 April 2022 (EDT)

GNU Emacs 28

2022-04-06T10:23:46Z

Elvince: release notes

https://www.gnu.org/software/emacs/#Releases

https://www.gnu.org/software/emacs/news/NEWS.28.1

https://www.masteringemacs.org/article/whats-new-in-emacs-28-1

= What's new in Emacs 28 =

Emacs 28.1 has a wide variety of new features, including:

* Native compilation of Lisp files
* Text shaping with HarfBuzz and drawing with Cairo
* Support for loading Secure Computing filters
* Much improved display of Emoji and Emoji sequences
* New system for documenting groups of functions
* A minor mode for context menus
* Mode-specific commands
* Emacs shows matching parentheses by default
* Many improvements and extensions to project.el

Main Page

2022-04-06T10:18:11Z

Elvince: Emacs 28.1

'''WikEmacs''' is here to stay. Spread the word!

[[File:Emacs_parts.png|320px|thumb|right|Basic [[Emacs Terminology|terminology]] of typical Emacs GUI Frame]]
__NOTOC__
'''First time visitors''' can start [[#Explore WikEmacs|exploring WikEmacs]]. We have added lots of useful pages since the launch of WikEmacs.

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

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

* Priority tasks
** 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.
* Intermediate tasks
** Provide tutorials or content for the [[:Category:Popular Package|popular packages]] or [[:Category:Built-in Package|built-in packages]].
** Add more content to [[Special:ShortPages|short pages]].
** Document or add more [[:Category:Third Party Package|third party packages]].
* Other tasks
** Copy edit [[Special:RecentChanges|recent changes]] or be a moral police.
** Add more members to various [[Special:Categories|categories]].
** Categorize one of these pages [[Special:UncategorizedPages|uncategorized pages]].
** 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).

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

The latest stable release of Emacs is [[GNU Emacs 28|Emacs-28.1]] released on April 4th, 2022. The precedent is [[GNU Emacs 27|Emacs-27.2]].

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]].

<div style="float: left; width: 49%;">
== Explore WikEmacs ==

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

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

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

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

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

</div>

<div style="float: right; width: 49%;">

==Help build WikEmacs==

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.)



* [[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])
* [[Built-in help]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html])
* [[Registers]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Registers.html])
* [[:Category:Search|Search for text in a buffer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Search.html])
* [[Fixing typos]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Fixit.html])
* [[Keyboard macros]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Keyboard-Macros.html])
* [[Windows within a frame]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Windows.html])
* [[Frames]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html])
* [[International character sets]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/International.html])
* [[Indentation]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Indentation.html])
* [[Editing source code]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Programs.html])
* [[Building software]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Building.html])
* [[Maintaining source code repositories]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Maintaining.html])
* [[Abbrevs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Abbrevs.html])
* [[Dired]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Dired.html])
* [[Calendars and diaries]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Calendar_002fDiary.html])
* [[Sending mail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Mail.html])
* [[Rmail]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html])
* [[Gnus]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Gnus.html])
* [[Document viewer]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Document-View.html])
* [[Shell commands withing Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Shell.html])
* [[Emacs server]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emacs-Server.html])
* [[Printing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Printing.html])
* [[Sorting]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Sorting.html])
* [[Picture mode]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Picture-Mode.html])
* [[Editing binary files]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Editing-Binary-Files.html])
* [[Saving Emacs sessions]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Emacs-Sessions.html])
* [[Recursive editing]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Recursive-Edit.html])
* [[Emulating other text editors]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Emulation.html])
* [[Hyperlinking within Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Hyperlinking.html])
* [[Games and fun]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Amusements.html])
* [[Installing additional packages]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Packages.html])
* [[Customising Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Customization.html])
** [[Customize]] (simple interface) ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Easy-Customization.html])
* [[Cancelling commands]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Quitting.html])
* [[If Emacs is malfunctioning]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Lossage.html])
* [[Reporting bugs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html])
* [[Contributing to GNU Emacs]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html])
* [[Getting help from others]] ([https://www.gnu.org/software/emacs/manual/html_node/emacs/Service.html])

[[Category:WikEmacs]]

Dired

2021-11-05T13:12:47Z

Elvince: /* See Also */ add filetree image

{{Package
|name=Dired
|description=File Manager for Emacs.
|source=http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/dired.el
|author=Sebastian Kremer
|maintainer=[[FSF]]
|in_emacs=yes
|Development status=active
}}

'''Dired''' is a inbuilt File Manager for Emacs. Its arguably the best
file manager with the functionality it possesses. Unlike any other
file managers the directory listing is just as an another [[buffer]] of
Emacs with '''dired-mode''' as {{ModeLink|Major Mode}}.

== Usage ==
'''Dired''' has countless functionality. The best way to learn it is to try it out. Open a dired buffer and look at the commands listed in the menus.

; {{CommandKeys|C-x d| dired}}
: ask for a directory and puts you into a buffer with direct listing of that directory.

; {{CommandKeys|C-x C-j| dired-jump}}
: jump to a dired buffer corresponding to the current buffer (This require loading [http://www.gnu.org/software/emacs/manual/html_node/dired-x/ Dired Extra]).

In the minibuffer, while doing 'Find File':

; {{Keys|C-d}}
: jump to a dired buffer corresponding to the directory in the minibuffer.

== Basic commands ==

; {{Keys| RET}}
: Open the file/Directory. You can use '''a''' to open the directory without creating another buffer.

; {{Keys| q}}
: Close the dir

; {{Keys| i}}
: i: open directory in subtree. Use '''^''' to go up one level. With a prefix argument ('''C-u i'''), you can edit the ''ls'' switches used for the listing. So you can add '''R''' to expand the whole tree starting at this subdirectory.

; {{keys|C}}
: Copy file
If you set <code>(setq dired-dwim-target t)</code>, split your window and open another dired buffer on the other window, Dired will suggest it as the default target directory for the copy and rename commands.

; {{Keys|R}}
:Rename file

; {{Keys|D}}
: Delete file

; {{Keys|+}}
: create a new dir

== Mark/unmark files ==

{{Keys|m}}
: mark a file

{{Keys|u}}
: unmark a file

{{Keys|U}}
: unmark all marked

{{Keys|%m}}
: mark by pattern

== Edit filenames and permissions ==

'''Wdired''' mode (writable dired) allows you to enter a mode where you can edit filenames, symbolic link target and filenames permissions as you would in a regular buffer. It is particularly great to do some editing based on search and replace.

{{Keys|C-x C-q}}
: enter wdired mode (calls ''wdired-change-to-wdired-mode''). Type '''C-c C-c''' to validate your changes or '''C-c ESC''' to abort.

{{Command|customize-group RET wdired}} to customize wdired behavior.

'''Note:''' in Dired, you can rename a single file or move the marked ones with '''R'''.

== Sort files ==

By default, typing '''s''' will toggle sorting by date. You can change the listing switches (of GNU '''ls''') with '''C-u s'''.

You can customize the variable '''dired-listing-switches'''. For example,

(setq dired-listing-switches "-aBhl --group-directories-first")

will display directories first. You can then customize per-directory local variables.

Dired+ (see below) offers more options (sort by size, by extension,…) and will add a menu entry.

== Find files recursively ==

=== find-name-dired ===

With {{Command|find-name-dired}}, you'll be asked for the base directory, a file wildcard and the matching files will be displayed in a Dired buffer. It uses the ''find'' GNU utility.

Similar commands are '''find-grep-dired''' or '''find-dired'''. More information can be read in [http://www.gnu.org/software/emacs/manual/html_node/emacs/Dired-and-Find.html#Dired-and-Find the documentation].

=== Interactive selection with Projectile ===

[[Projectile]], coupled with {{Command|helm-projectile}}, lets you find recursively and interactively files in your project. This command does not use a Dired buffer.

== View image thumbnails (image-dired) ==

Viewing images is a builtin feature of Dired (press Enter or '''v''' on an image file). On Emacs24.4, pressing '''n''' and '''p''' will show the next or previous image file. But if you want to navigate between image thumbnails, use the (builtin too) [http://www.gnu.org/software/emacs/manual/html_node/emacs/Image_002dDired.html image-dired]. You can directly call it with {{Command|image-dired}}, or mark the images you want to look at in the dired buffer (with '''m''') and then type '''C-t d (image-dired-display-thumbs)'''.

=== Tag images ===

More advanced features include image tags, which are metadata used to categorize image files. The tags are stored in a plain text file configured by '''image-dired-db-file'''.

To tag image files, mark them in the dired buffer and type '''C-t t (image-dired-tag-files)'''. This reads the tag name in the minibuffer.

To mark files having a certain tag, type '''C-t f (image-dired-mark-tagged-files)'''. After marking image files with a certain tag, you can use '''C-t d''' to view them.

You can also tag a file directly from the thumbnail buffer by typing '''t t''' and you can remove a tag by typing '''t r'''.

There is also a special “tag” called “comment” for each file (it is not a tag in the exact same sense as the other tags, it is handled slightly different). That is used to enter a comment or description about the image. You comment a file from the thumbnail buffer by typing '''c'''. You will be prompted for a comment. Type '''C-t c''' to add a comment from Dired '''(image-dired-dired-comment-files)'''.

=== Rotate images ===

Image-Dired also provides simple image manipulation. In the thumbnail buffer, type '''L''' to rotate the original image 90 degrees anti clockwise, and '''R''' to rotate it 90 degrees clockwise. This rotation is lossless, and uses an external utility called JpegTRAN.

=== See also: Dired Image SlideShow (DISS) ===

[https://github.com/ieure/diss DISS] is an external package, published in 2021, that builds on Dired and Image-mode to provide a mode to browse images and view them in a slideshow.

Diss features include:

* Use any Dired buffer (including find-dired) as the source of images.
* Manual navigation, or automatic advance with delay.
* Easily categorize files: mark, flag for deletion, or apply an arbitrary marker character directly from the image.
* Advancing images can optionally apply a marker to every image.
* Infinite loop, or pop back to image list when finished.
* Multiple slideshow configurations can be named and saved.
* Quick image tools: Rotate CW/CCW, smart fit, fit height, fit width, rename.

It can also work with the lightweight Feh image viewer.

== See Also ==

=== [[Dired+]] - a package that extends the functionalities of Dired ===

=== [[Direx]] - a general purpose directory/tree explorer ===

=== Dired-du - display recursive directory sizes ===

[https://elpa.gnu.org/packages/dired-du.html Dired-du] (in GNU [[ELPA]]) defines a minor mode '''dired-du-mode''' to show
the recursive size of directories in Dired buffers.
If the <code>du</code> program is available, then the directory sizes are
obtained with it. Otherwise, the directory sizes are obtained
with Lisp. The former is faster and provide a more precise value.
For directories where the user doesn't have read permission,
the recursive size is not obtained.
Once this mode is enabled, every new Dired buffer displays
recursive dir sizes.

To enable the mode at start up add the following into your [[Init File]]:

(add-hook 'dired-mode-hook #'dired-du-mode)

but beware that it can take a long time.

So you can also enable this mode once in a buffer: '''M-x dired-du-mode''', and disable it when you're done.

You can also select files (with the selector <code>*</code> for example) and call '''M-x dired-du-count-sizes''', to count the number of marked files and how much space they use.

=== Dired-details - a library to make file details hide-able ===

=== [https://github.com/Fuco1/dired-hacks#dired-open dired-open] - open files with external applications ===

Many times, you want to open media files, pdfs or other documents with an external application. There's remedy for that too, namely dired-guess-shell-alist-user, but that is still not as convenient as just hitting enter.

dired-open is part of dired-hacks (in MELPA).

This feature is also the goal of [https://melpa.org/#/openwith openwith] (in MELPA).

=== Dired-k - add colored icons depending on the git status ===

See here: http://wikemacs.org/wiki/Git#Colorize_Dired_output_depending_on_the_file_git_status

=== [https://github.com/Fuco1/dired-hacks dired-subtree] - insert the subdirectory (with the i key) directly below its line ===

=== Treemacs, a tree-style file explorer ===

see [https://github.com/Alexander-Miller/treemacs Treemacs]. It has optional git integration (showing the status of files with different faces), optional follow-mode, projectile integration (quickly open treemacs at any known project’s root directory), session persistence with <code>desktop-save-mode</code>, and more.

=== [[Speed_bar]] - navigate files and sources in another frame ===

=== [[emacs-nav]] - a simple files and sources browser popup ===

=== [http://melpa.org/#/dirtree dirtree] - a directory tree view panel ===

=== [https://github.com/asok/peep-dired peep-dired] - file previews à la ranger ===

[http://ranger.nongnu.org/ Ranger] is a file browser for the terminal that has a nice navigation system composed of three panes: the current directory at the middle, the previous one to the left, and a preview of the file the cursor is on to the right. Peep-dired mimics a handy two-panes navigation with instant preview.

=== [https://github.com/ralesi/ranger.el Ranger]- Ranger functionalities in Dired ===

With ranger (formerly known as evil-ranger, even if it wasn't specific to evil-mode), we have most of ranger's functionalities in Dired: 3 panes layout, previews, etc. Very nice !

[[File:Evil-ranger-preview.png|800px]]

=== [https://github.com/knpatel401/filetree file-tree] - display and operate and a file list as a tree ===

'''file-tree''' offers two things: it's a file tree viewer, and it allows to write and display ```notes``` associated to files.

It offers actions similar to Dired: mark files and take actions (copy, delete, rename…).

You can find a demo video on Youtube here: https://youtu.be/-KrMaLq8Bms

[[File:Filetree.jpg|800px]]

[[Category:Desktop Management]] [[Category:File Manager]][[Category:Built-in Package]]
[[Category:Beginner]]
[[Category:Navigation]]

File:Filetree.jpg

2021-11-05T13:11:36Z

Elvince: The filetree default view. One can cycle between notes, icons, directory info, tree depth…

== Summary ==
The filetree default view. One can cycle between notes, icons, directory info, tree depth…

Dired

2021-11-05T13:10:38Z

Elvince: /* See Also */ fix img

{{Package
|name=Dired
|description=File Manager for Emacs.
|source=http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/dired.el
|author=Sebastian Kremer
|maintainer=[[FSF]]
|in_emacs=yes
|Development status=active
}}

'''Dired''' is a inbuilt File Manager for Emacs. Its arguably the best
file manager with the functionality it possesses. Unlike any other
file managers the directory listing is just as an another [[buffer]] of
Emacs with '''dired-mode''' as {{ModeLink|Major Mode}}.

== Usage ==
'''Dired''' has countless functionality. The best way to learn it is to try it out. Open a dired buffer and look at the commands listed in the menus.

; {{CommandKeys|C-x d| dired}}
: ask for a directory and puts you into a buffer with direct listing of that directory.

; {{CommandKeys|C-x C-j| dired-jump}}
: jump to a dired buffer corresponding to the current buffer (This require loading [http://www.gnu.org/software/emacs/manual/html_node/dired-x/ Dired Extra]).

In the minibuffer, while doing 'Find File':

; {{Keys|C-d}}
: jump to a dired buffer corresponding to the directory in the minibuffer.

== Basic commands ==

; {{Keys| RET}}
: Open the file/Directory. You can use '''a''' to open the directory without creating another buffer.

; {{Keys| q}}
: Close the dir

; {{Keys| i}}
: i: open directory in subtree. Use '''^''' to go up one level. With a prefix argument ('''C-u i'''), you can edit the ''ls'' switches used for the listing. So you can add '''R''' to expand the whole tree starting at this subdirectory.

; {{keys|C}}
: Copy file
If you set <code>(setq dired-dwim-target t)</code>, split your window and open another dired buffer on the other window, Dired will suggest it as the default target directory for the copy and rename commands.

; {{Keys|R}}
:Rename file

; {{Keys|D}}
: Delete file

; {{Keys|+}}
: create a new dir

== Mark/unmark files ==

{{Keys|m}}
: mark a file

{{Keys|u}}
: unmark a file

{{Keys|U}}
: unmark all marked

{{Keys|%m}}
: mark by pattern

== Edit filenames and permissions ==

'''Wdired''' mode (writable dired) allows you to enter a mode where you can edit filenames, symbolic link target and filenames permissions as you would in a regular buffer. It is particularly great to do some editing based on search and replace.

{{Keys|C-x C-q}}
: enter wdired mode (calls ''wdired-change-to-wdired-mode''). Type '''C-c C-c''' to validate your changes or '''C-c ESC''' to abort.

{{Command|customize-group RET wdired}} to customize wdired behavior.

'''Note:''' in Dired, you can rename a single file or move the marked ones with '''R'''.

== Sort files ==

By default, typing '''s''' will toggle sorting by date. You can change the listing switches (of GNU '''ls''') with '''C-u s'''.

You can customize the variable '''dired-listing-switches'''. For example,

(setq dired-listing-switches "-aBhl --group-directories-first")

will display directories first. You can then customize per-directory local variables.

Dired+ (see below) offers more options (sort by size, by extension,…) and will add a menu entry.

== Find files recursively ==

=== find-name-dired ===

With {{Command|find-name-dired}}, you'll be asked for the base directory, a file wildcard and the matching files will be displayed in a Dired buffer. It uses the ''find'' GNU utility.

Similar commands are '''find-grep-dired''' or '''find-dired'''. More information can be read in [http://www.gnu.org/software/emacs/manual/html_node/emacs/Dired-and-Find.html#Dired-and-Find the documentation].

=== Interactive selection with Projectile ===

[[Projectile]], coupled with {{Command|helm-projectile}}, lets you find recursively and interactively files in your project. This command does not use a Dired buffer.

== View image thumbnails (image-dired) ==

Viewing images is a builtin feature of Dired (press Enter or '''v''' on an image file). On Emacs24.4, pressing '''n''' and '''p''' will show the next or previous image file. But if you want to navigate between image thumbnails, use the (builtin too) [http://www.gnu.org/software/emacs/manual/html_node/emacs/Image_002dDired.html image-dired]. You can directly call it with {{Command|image-dired}}, or mark the images you want to look at in the dired buffer (with '''m''') and then type '''C-t d (image-dired-display-thumbs)'''.

=== Tag images ===

More advanced features include image tags, which are metadata used to categorize image files. The tags are stored in a plain text file configured by '''image-dired-db-file'''.

To tag image files, mark them in the dired buffer and type '''C-t t (image-dired-tag-files)'''. This reads the tag name in the minibuffer.

To mark files having a certain tag, type '''C-t f (image-dired-mark-tagged-files)'''. After marking image files with a certain tag, you can use '''C-t d''' to view them.

You can also tag a file directly from the thumbnail buffer by typing '''t t''' and you can remove a tag by typing '''t r'''.

There is also a special “tag” called “comment” for each file (it is not a tag in the exact same sense as the other tags, it is handled slightly different). That is used to enter a comment or description about the image. You comment a file from the thumbnail buffer by typing '''c'''. You will be prompted for a comment. Type '''C-t c''' to add a comment from Dired '''(image-dired-dired-comment-files)'''.

=== Rotate images ===

Image-Dired also provides simple image manipulation. In the thumbnail buffer, type '''L''' to rotate the original image 90 degrees anti clockwise, and '''R''' to rotate it 90 degrees clockwise. This rotation is lossless, and uses an external utility called JpegTRAN.

=== See also: Dired Image SlideShow (DISS) ===

[https://github.com/ieure/diss DISS] is an external package, published in 2021, that builds on Dired and Image-mode to provide a mode to browse images and view them in a slideshow.

Diss features include:

* Use any Dired buffer (including find-dired) as the source of images.
* Manual navigation, or automatic advance with delay.
* Easily categorize files: mark, flag for deletion, or apply an arbitrary marker character directly from the image.
* Advancing images can optionally apply a marker to every image.
* Infinite loop, or pop back to image list when finished.
* Multiple slideshow configurations can be named and saved.
* Quick image tools: Rotate CW/CCW, smart fit, fit height, fit width, rename.

It can also work with the lightweight Feh image viewer.

== See Also ==

=== [[Dired+]] - a package that extends the functionalities of Dired ===

=== [[Direx]] - a general purpose directory/tree explorer ===

=== Dired-du - display recursive directory sizes ===

[https://elpa.gnu.org/packages/dired-du.html Dired-du] (in GNU [[ELPA]]) defines a minor mode '''dired-du-mode''' to show
the recursive size of directories in Dired buffers.
If the <code>du</code> program is available, then the directory sizes are
obtained with it. Otherwise, the directory sizes are obtained
with Lisp. The former is faster and provide a more precise value.
For directories where the user doesn't have read permission,
the recursive size is not obtained.
Once this mode is enabled, every new Dired buffer displays
recursive dir sizes.

To enable the mode at start up add the following into your [[Init File]]:

(add-hook 'dired-mode-hook #'dired-du-mode)

but beware that it can take a long time.

So you can also enable this mode once in a buffer: '''M-x dired-du-mode''', and disable it when you're done.

You can also select files (with the selector <code>*</code> for example) and call '''M-x dired-du-count-sizes''', to count the number of marked files and how much space they use.

=== Dired-details - a library to make file details hide-able ===

=== [https://github.com/Fuco1/dired-hacks#dired-open dired-open] - open files with external applications ===

Many times, you want to open media files, pdfs or other documents with an external application. There's remedy for that too, namely dired-guess-shell-alist-user, but that is still not as convenient as just hitting enter.

dired-open is part of dired-hacks (in MELPA).

This feature is also the goal of [https://melpa.org/#/openwith openwith] (in MELPA).

=== Dired-k - add colored icons depending on the git status ===

See here: http://wikemacs.org/wiki/Git#Colorize_Dired_output_depending_on_the_file_git_status

=== [https://github.com/Fuco1/dired-hacks dired-subtree] - insert the subdirectory (with the i key) directly below its line ===

=== Treemacs, a tree-style file explorer ===

see [https://github.com/Alexander-Miller/treemacs Treemacs]. It has optional git integration (showing the status of files with different faces), optional follow-mode, projectile integration (quickly open treemacs at any known project’s root directory), session persistence with <code>desktop-save-mode</code>, and more.

=== [[Speed_bar]] - navigate files and sources in another frame ===

=== [[emacs-nav]] - a simple files and sources browser popup ===

=== [http://melpa.org/#/dirtree dirtree] - a directory tree view panel ===

=== [https://github.com/asok/peep-dired peep-dired] - file previews à la ranger ===

[http://ranger.nongnu.org/ Ranger] is a file browser for the terminal that has a nice navigation system composed of three panes: the current directory at the middle, the previous one to the left, and a preview of the file the cursor is on to the right. Peep-dired mimics a handy two-panes navigation with instant preview.

=== [https://github.com/ralesi/ranger.el Ranger]- Ranger functionalities in Dired ===

With ranger (formerly known as evil-ranger, even if it wasn't specific to evil-mode), we have most of ranger's functionalities in Dired: 3 panes layout, previews, etc. Very nice !

[[File:Evil-ranger-preview.png|800px]]

=== [https://github.com/knpatel401/filetree file-tree] - display and operate and a file list as a tree ===

```file-tree``` offers two things: it's a file tree viewer, and it allows to write and display ```notes``` associated to files.

It offers actions similar to Dired: mark files and take actions (copy, delete, rename…).

You can find a demo video on Youtube here: https://youtu.be/-KrMaLq8Bms

[[Category:Desktop Management]] [[Category:File Manager]][[Category:Built-in Package]]
[[Category:Beginner]]
[[Category:Navigation]]

Dired

2021-11-05T13:09:57Z

Elvince: /* See Also */ add filetree

{{Package
|name=Dired
|description=File Manager for Emacs.
|source=http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/dired.el
|author=Sebastian Kremer
|maintainer=[[FSF]]
|in_emacs=yes
|Development status=active
}}

'''Dired''' is a inbuilt File Manager for Emacs. Its arguably the best
file manager with the functionality it possesses. Unlike any other
file managers the directory listing is just as an another [[buffer]] of
Emacs with '''dired-mode''' as {{ModeLink|Major Mode}}.

== Usage ==
'''Dired''' has countless functionality. The best way to learn it is to try it out. Open a dired buffer and look at the commands listed in the menus.

; {{CommandKeys|C-x d| dired}}
: ask for a directory and puts you into a buffer with direct listing of that directory.

; {{CommandKeys|C-x C-j| dired-jump}}
: jump to a dired buffer corresponding to the current buffer (This require loading [http://www.gnu.org/software/emacs/manual/html_node/dired-x/ Dired Extra]).

In the minibuffer, while doing 'Find File':

; {{Keys|C-d}}
: jump to a dired buffer corresponding to the directory in the minibuffer.

== Basic commands ==

; {{Keys| RET}}
: Open the file/Directory. You can use '''a''' to open the directory without creating another buffer.

; {{Keys| q}}
: Close the dir

; {{Keys| i}}
: i: open directory in subtree. Use '''^''' to go up one level. With a prefix argument ('''C-u i'''), you can edit the ''ls'' switches used for the listing. So you can add '''R''' to expand the whole tree starting at this subdirectory.

; {{keys|C}}
: Copy file
If you set <code>(setq dired-dwim-target t)</code>, split your window and open another dired buffer on the other window, Dired will suggest it as the default target directory for the copy and rename commands.

; {{Keys|R}}
:Rename file

; {{Keys|D}}
: Delete file

; {{Keys|+}}
: create a new dir

== Mark/unmark files ==

{{Keys|m}}
: mark a file

{{Keys|u}}
: unmark a file

{{Keys|U}}
: unmark all marked

{{Keys|%m}}
: mark by pattern

== Edit filenames and permissions ==

'''Wdired''' mode (writable dired) allows you to enter a mode where you can edit filenames, symbolic link target and filenames permissions as you would in a regular buffer. It is particularly great to do some editing based on search and replace.

{{Keys|C-x C-q}}
: enter wdired mode (calls ''wdired-change-to-wdired-mode''). Type '''C-c C-c''' to validate your changes or '''C-c ESC''' to abort.

{{Command|customize-group RET wdired}} to customize wdired behavior.

'''Note:''' in Dired, you can rename a single file or move the marked ones with '''R'''.

== Sort files ==

By default, typing '''s''' will toggle sorting by date. You can change the listing switches (of GNU '''ls''') with '''C-u s'''.

You can customize the variable '''dired-listing-switches'''. For example,

(setq dired-listing-switches "-aBhl --group-directories-first")

will display directories first. You can then customize per-directory local variables.

Dired+ (see below) offers more options (sort by size, by extension,…) and will add a menu entry.

== Find files recursively ==

=== find-name-dired ===

With {{Command|find-name-dired}}, you'll be asked for the base directory, a file wildcard and the matching files will be displayed in a Dired buffer. It uses the ''find'' GNU utility.

Similar commands are '''find-grep-dired''' or '''find-dired'''. More information can be read in [http://www.gnu.org/software/emacs/manual/html_node/emacs/Dired-and-Find.html#Dired-and-Find the documentation].

=== Interactive selection with Projectile ===

[[Projectile]], coupled with {{Command|helm-projectile}}, lets you find recursively and interactively files in your project. This command does not use a Dired buffer.

== View image thumbnails (image-dired) ==

Viewing images is a builtin feature of Dired (press Enter or '''v''' on an image file). On Emacs24.4, pressing '''n''' and '''p''' will show the next or previous image file. But if you want to navigate between image thumbnails, use the (builtin too) [http://www.gnu.org/software/emacs/manual/html_node/emacs/Image_002dDired.html image-dired]. You can directly call it with {{Command|image-dired}}, or mark the images you want to look at in the dired buffer (with '''m''') and then type '''C-t d (image-dired-display-thumbs)'''.

=== Tag images ===

More advanced features include image tags, which are metadata used to categorize image files. The tags are stored in a plain text file configured by '''image-dired-db-file'''.

To tag image files, mark them in the dired buffer and type '''C-t t (image-dired-tag-files)'''. This reads the tag name in the minibuffer.

To mark files having a certain tag, type '''C-t f (image-dired-mark-tagged-files)'''. After marking image files with a certain tag, you can use '''C-t d''' to view them.

You can also tag a file directly from the thumbnail buffer by typing '''t t''' and you can remove a tag by typing '''t r'''.

There is also a special “tag” called “comment” for each file (it is not a tag in the exact same sense as the other tags, it is handled slightly different). That is used to enter a comment or description about the image. You comment a file from the thumbnail buffer by typing '''c'''. You will be prompted for a comment. Type '''C-t c''' to add a comment from Dired '''(image-dired-dired-comment-files)'''.

=== Rotate images ===

Image-Dired also provides simple image manipulation. In the thumbnail buffer, type '''L''' to rotate the original image 90 degrees anti clockwise, and '''R''' to rotate it 90 degrees clockwise. This rotation is lossless, and uses an external utility called JpegTRAN.

=== See also: Dired Image SlideShow (DISS) ===

[https://github.com/ieure/diss DISS] is an external package, published in 2021, that builds on Dired and Image-mode to provide a mode to browse images and view them in a slideshow.

Diss features include:

* Use any Dired buffer (including find-dired) as the source of images.
* Manual navigation, or automatic advance with delay.
* Easily categorize files: mark, flag for deletion, or apply an arbitrary marker character directly from the image.
* Advancing images can optionally apply a marker to every image.
* Infinite loop, or pop back to image list when finished.
* Multiple slideshow configurations can be named and saved.
* Quick image tools: Rotate CW/CCW, smart fit, fit height, fit width, rename.

It can also work with the lightweight Feh image viewer.

== See Also ==

=== [[Dired+]] - a package that extends the functionalities of Dired ===

=== [[Direx]] - a general purpose directory/tree explorer ===

=== Dired-du - display recursive directory sizes ===

[https://elpa.gnu.org/packages/dired-du.html Dired-du] (in GNU [[ELPA]]) defines a minor mode '''dired-du-mode''' to show
the recursive size of directories in Dired buffers.
If the <code>du</code> program is available, then the directory sizes are
obtained with it. Otherwise, the directory sizes are obtained
with Lisp. The former is faster and provide a more precise value.
For directories where the user doesn't have read permission,
the recursive size is not obtained.
Once this mode is enabled, every new Dired buffer displays
recursive dir sizes.

To enable the mode at start up add the following into your [[Init File]]:

(add-hook 'dired-mode-hook #'dired-du-mode)

but beware that it can take a long time.

So you can also enable this mode once in a buffer: '''M-x dired-du-mode''', and disable it when you're done.

You can also select files (with the selector <code>*</code> for example) and call '''M-x dired-du-count-sizes''', to count the number of marked files and how much space they use.

=== Dired-details - a library to make file details hide-able ===

=== [https://github.com/Fuco1/dired-hacks#dired-open dired-open] - open files with external applications ===

Many times, you want to open media files, pdfs or other documents with an external application. There's remedy for that too, namely dired-guess-shell-alist-user, but that is still not as convenient as just hitting enter.

dired-open is part of dired-hacks (in MELPA).

This feature is also the goal of [https://melpa.org/#/openwith openwith] (in MELPA).

=== Dired-k - add colored icons depending on the git status ===

See here: http://wikemacs.org/wiki/Git#Colorize_Dired_output_depending_on_the_file_git_status

=== [https://github.com/Fuco1/dired-hacks dired-subtree] - insert the subdirectory (with the i key) directly below its line ===

=== Treemacs, a tree-style file explorer ===

see [https://github.com/Alexander-Miller/treemacs Treemacs]. It has optional git integration (showing the status of files with different faces), optional follow-mode, projectile integration (quickly open treemacs at any known project’s root directory), session persistence with <code>desktop-save-mode</code>, and more.

=== [[Speed_bar]] - navigate files and sources in another frame ===

=== [[emacs-nav]] - a simple files and sources browser popup ===

=== [http://melpa.org/#/dirtree dirtree] - a directory tree view panel ===

=== [https://github.com/asok/peep-dired peep-dired] - file previews à la ranger ===

[http://ranger.nongnu.org/ Ranger] is a file browser for the terminal that has a nice navigation system composed of three panes: the current directory at the middle, the previous one to the left, and a preview of the file the cursor is on to the right. Peep-dired mimics a handy two-panes navigation with instant preview.

=== [https://github.com/ralesi/ranger.el Ranger]- Ranger functionalities in Dired ===

With ranger (formerly known as evil-ranger, even if it wasn't specific to evil-mode), we have most of ranger's functionalities in Dired: 3 panes layout, previews, etc. Very nice !

=== [https://github.com/knpatel401/filetree file-tree] - display and operate and a file list as a tree ===

```file-tree``` offers two things: it's a file tree viewer, and it allows to write and display ```notes``` associated to files.

It offers actions similar to Dired: mark files and take actions (copy, delete, rename…).

You can find a demo video on Youtube here: https://youtu.be/-KrMaLq8Bms

[[File:Evil-ranger-preview.png|800px]]

[[Category:Desktop Management]] [[Category:File Manager]][[Category:Built-in Package]]
[[Category:Beginner]]
[[Category:Navigation]]

User talk:JorgePeixoto

2021-10-10T23:47:30Z

Elvince: Hello!

Hello Jorge, welcome on the small team of Wikemacs contributors! [[User:Elvince|Elvince]] ([[User talk:Elvince|talk]]) 19:47, 10 October 2021 (EDT)