Fork us on GitHub Follow us on Facebook Follow us on Twitter

Opened 7 years ago

Closed 4 years ago

#513 closed enhancement (wontfix)

Porting Emacs Editor to HelenOS

Reported by: Pratik Mankawde Owned by: Pratik Mankawde
Priority: major Milestone:
Component: helenos/app/other Version:
Keywords: Porting, Emacs, Text Editor, Word Processor Cc: Pratik Mankawde, Anjali, sahitya, sindhu, sin.sin.1991@…
Blocker for: Depends on:
See also: #413, #403

Description (last modified by Vojtech Horky)

Details
Emacs text editor is very extensible and customizable text editor. It supports a range of features from word processing, program development to rss reader. In background it uses Emacs Lisp interpreter to execute all functions implemented as Emacs lisp scripts. We are trying to port Emacs text editor to HelenOS. Firstly we will try to port the terminal version with minimal functionality and then we will try to add functionality to it.

What Gains and Benefits will this bring?
Currently HelenOS has "edit" as simple text editor. As much as HelenOS is moving towards becoming self-hosting, it will need some utility for writing code, publishing documentation etc. Emacs Text Editor is a great option for this purpose.

Difficulty
Medium to Hard

Required Skills
Programming in the C, Python, Emacs Lisp languages.
Working Experience in non-POSIX environment.

Change History (7)

comment:1 Changed 7 years ago by Pratik Mankawde

Status: newaccepted

comment:2 Changed 7 years ago by Jakub Jermář

Milestone: 0.5.1
Version: mainline

Removing this ticket from the 0.5.1 milestone and mainline version.

I was also wondering whether the submitter is well aware of the scope of this endeavor. My particular concern here would be the amount of Emacs dependencies that would have to be ported to and maintained in HelenOS.

I am also not convinced about the usefulness of Emacs in HelenOS. Using edit to edit source files is quite easy and I believe it will be easier to enhance and maintain edit rather than committing to support Emacs and its dependencies. There is also no point in porting all the non-essential GNU software to HelenOS as our goal is not to make a better GNU than GNU itself.

Having said that, I am perfectly okay with someone working on this ticket for the training's sake, but the prospect of having Emacs integrated into HelenOS and maintaining it there seems quite low.

Btw, why don't you guys write to the ML first? It's much more comfortable to talk about the HelenOS project priorities there than om a comment section of a ticket.

comment:3 Changed 7 years ago by Sahitya Sindhu

Cc: sin.sin.1991@… added

comment:4 Changed 7 years ago by Vojtech Horky

Depends on: Porting GCC http://trac.helenos.org/ticket/413, Porting Python http://trac.helenos.org/ticket/403
Description: modified (diff)
See also: #413, #403

comment:5 Changed 7 years ago by Vojtech Horky

I do not think that Python is needed and, strictly speaking, native GCC is not needed as well as it shall be possible to cross-compile all the dependencies.

comment:6 in reply to:  5 Changed 7 years ago by Pratik Mankawde

Replying to vhotspur:

I do not think that Python is needed …

We are trying to compile Emacs using GCC cross compiler only. Although Emacs has LISP dependencies as most of the features are implemented as dynamically loadable LISP scripts, and we are not able to figure out how to handle them yet. We will appreciate any kind of suggestions in this regard. Moreover about python, some scripts included in Emacs source code are written in python, that's why added 'porting python' section with this link. Although thanks for the information.

Last edited 7 years ago by Pratik Mankawde (previous) (diff)

comment:7 Changed 4 years ago by Jakub Jermář

Resolution: wontfix
Status: acceptedclosed

Closing as will-not-fix. There is no demand for this functionality and the ticket is not being worked on anyway.

Note: See TracTickets for help on using tickets.