Talk:Emacs
| This is the talk page for discussing improvements to the Emacs article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Archives: 1, 2Auto-archiving period: 2 years |
| Emacs is a former featured article. Please see the links under Article milestones below for its original nomination page (for older articles, check the nomination archive) and why it was removed. | |||||||||||||
| This article appeared on Wikipedia's Main Page as Today's featured article on October 4, 2004. | |||||||||||||
| |||||||||||||
| Current status: Former featured article | |||||||||||||
| This It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
|
This article contains broken links to one or more target anchors:
The anchors may have been removed, renamed, or are no longer valid. Please fix them by following the link above, checking the page history of the target pages, or updating the links. Remove this template after the problem is fixed | Report an error |
Author Images
How is it that 2/3 authors have their photographs on the page? It seems appropriate to have all three or none. 209.161.228.135 (talk) 01:40, 8 July 2023 (UTC)
- who is the third author? The article says there are two authors. both their pictures are present. there's even a picture of another developer who implemented EMAXlCS somewhere. 2601:547:B04:1D9E:D8C2:395C:9519:8266 (talk) 02:26, 8 July 2023 (UTC)
- "Steele and Stallman's finished implementation"
- The article actually mentions three authors, but is very unclear about David Moon's role. 2600:8802:5913:1700:3955:6DC8:9B6:DD5C (talk) 08:12, 9 October 2024 (UTC)
"Unlike most modern text editors, TECO used separate modes"
Eh? This is very much like vi and other modal editors. The paragraph ends with "This behavior is similar to that of the program ed" -- the editor from which vi was derived (via ex). vi was the "visual" version of ed. If the point of this paragraph is simply that TECO was a line editor rather than a visual buffer editor, there are far better ways of expressing/explaining it than conflating that distinction with the modal/modeless distinction. -- 2600:8802:5913:1700:3955:6DC8:9B6:DD5C (talk) 08:03, 9 October 2024 (UTC)
"Emacs pinky" listed at Redirects for discussion
The redirect Emacs pinky has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2025 January 18 § Emacs pinky until a consensus is reached. 1234qwer1234qwer4 16:20, 18 January 2025 (UTC)
emacs vs GNU emacs
A lot of this article talks about things specific to GNU emacs, when other implementations exist without these features. There's a GNU emacs article as well, so shouldn't the emacs article be for emacsen as a whole? mgjertson (talk) (contribs) 15:49, 9 December 2025 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.


