Revision as of 01:29, 27 May 2005 editOmegatron (talk | contribs)Administrators35,798 edits plugins← Previous edit | Revision as of 23:51, 8 June 2005 edit undo206.124.132.18 (talk)No edit summaryNext edit → | ||
Line 102: | Line 102: | ||
jedit does have spell checking, but it's a plugin. how should we indicate this? - ] 01:29, May 27, 2005 (UTC) | jedit does have spell checking, but it's a plugin. how should we indicate this? - ] 01:29, May 27, 2005 (UTC) | ||
:it is indicated (sort of). it says 'This table lists common basic features supported natively (i.e. without third-party add-ons)'. Plugins don't fall into that category, as far as I know - which is why it's marked as not having a spellchecker. the same is true for vim, and probably most of the other text editors being compared. |
Revision as of 23:51, 8 June 2005
Ack! Yet more questions about MDI
Several editors can edit multiple documents by displaying one document buffer and hiding the rest. This is similar to a tabbed window interface, except no tabs are shown.
Most of the vi clones support such a MDI, including vim and nvi. IIRC, even traditional vi has primitive support for such an interface.
Although I'm not an emacs user, I believe that XEmacs and GNU Emacs also can edit multiple files in a similar fashion.
Perhaps we need an 'other' column for MDI? Or we could call it 'tabless tabs' ;)
(Oopsie -- missed the comment by Smjg 14:34, 11 Mar 2005. He basically states the same thing.)
Serious suggestion: We add a 'hidden buffers' column to MDI.
- Yeah, the columns need to be reordered/redefined. In the table, there are some SDI editors with window splitting, but window splitting is placed under MDI. Look confusing. (Can we call them MDI when they have window splitting?) Minghong 09:40, 17 Mar 2005 (UTC)
- They should only have a 'Yes' in this column if they actually allow the panes of the split window to display different documents at the same time. -- Smjg 11:22, 17 Mar 2005 (UTC)
Shell integration and Column mode editing
I haven't changed the 'shell integration' values for vi or vim, but doesn't the '!' command (run shell command) count as shell integration for vi/vim? I left the value as 'N/A', since I may be misunderstanding shell integration.
Could someone please clarify this?
In addition, wouldn't vim's 'visual mode' count as column mode editing, or am I missing something?
- Originally I added "shell integration" for text editors can add items on Windows Explorer's context menu. But now it seems to be not only GUI shell, but also command-line shell... I don't know about vim, but column edit mode refers to the ability to selection vertically . --Minghong 08:50, 9 Mar 2005 (UTC)
- In that case, the column title should be changed. Many people who use operating systems other than MS Windows will understand "shell integration" to mean the ability to start a shell from within the editor or to insert the output of system commands in the buffer. Burschik 15:22, 10 Mar 2005 (UTC)
Tabs
This should be probably multiple file handling, or multiple windows, since tabs aren't found in command line/curses based editors, to be fair. Dysprosia 22:32, 10 Mar 2005 (UTC)
- I agree
- Not agree, as the way to handling multiple document can be very different: 1) open multiple windows; 2) MDI; or 3) tabbed interface. There may be more, but tabbed interface is the most popular. (I don't mean I hate command-line editor thought) --Minghong 09:30, 11 Mar 2005 (UTC)
- I can think of
- multiple windows, similarly to many web browsers
- MDI
- split window
- tabbed interface or similar
- Moreover, some editors may support more than one way of displaying/opening multiple documents, or none at all. Some may have a system of switching between documents such that only one is on the screen at a time, but without the convenience of a tabbed interface (e.g. Emacs, which provides this independently of split window and GUI-mode multiple windows). There are also platform differences - an app that uses MDI on Windows may use separate windows in its Mac version, with this being how apps tend to work on Mac OS. And TextPad uses MDI, but has a document selector window that provides the convenience of a tabbed interface. -- Smjg 14:34, 11 Mar 2005 (UTC)
- I can think of
- Do we really need a column for SDI? Really it just means it has neither MDI nor TDI. Moreover, the fact that the SDI column follows the same colour scheme as the rest of the columns makes it look as though SDI is a positive feature, which doesn't strike me as right. Personally, I'd be inclined to get rid of the SDI column and move the others back to the basic features table.... -- Smjg 18:08, 15 Mar 2005 (UTC)
- Just because you don't think that SDI is the best doesn't mean that other people don't. For example, I think that SDI is vastly superiour to MDI. Since it is a subjective thing, it would not be fair to change it. --Ctachme 21:12, 15 Mar 2005 (UTC)
Better exaplanation of fields
The meaning of most columnts is rather unclear. Also some "features" don't apply to certain editors as they are implemented by other parts of the system but integrate seamlessly into the editor(spell checking in Unix editors is one example, a better example is ftpfs and webfs in Plan 9) Lost Goblin
16 references for just Emacs?!
We should better combine it into one reference of the Emacs manual... --Minghong 20:40, 11 Mar 2005 (UTC)
Windowing system integration
What is Windowing system integration? --Hhielscher 09:40, 12 Mar 2005 (UTC)
- Isn't that obvious? Integration with your windowing system, e.g. right-click at a file > Edit with Notepad. Originally that column was "shell integration". But under different platform, the term "shell" refers to different thing. --Minghong 19:44, 12 Mar 2005 (UTC)
- Anyway, I've found a better name. Take a look. --Minghong 19:51, 12 Mar 2005 (UTC)
- How can adding a registry entry by then installer(which only applies to windows, anyway) be considered a text editor feature? maybe something like Plumber (Plan 9) could be considered "Window system integration", but still I don't think it can be considered a feature of the text editor itself. Lost Goblin
- Not really. Most people don't know about registry. Even if they do, it is still nice that the editor itself can handle it (add/remove). Personally I won't use the use without shell integration, e.g. those Java-based text editors like jEdit. P.S. Someone should put jEdit in this comparison. Minghong 09:35, 17 Mar 2005 (UTC)
- How can adding a registry entry by then installer(which only applies to windows, anyway) be considered a text editor feature? maybe something like Plumber (Plan 9) could be considered "Window system integration", but still I don't think it can be considered a feature of the text editor itself. Lost Goblin
EDXOR is Win32
Why was the EDXOR column deleted? EDXOR is a Win32 application, with a Win16 version available as well. And, it's not THAT uncommon. --KelisFan2K5 21:49, 13 Mar 2005 (UTC)
- I never heard of it, can you provide references? papers? Lost Goblin
- http://members.ozemail.com.au/~nulifetv/freezip/freeware/edxor.htm <- This is the official EDXOR site. --KelisFan2K5 01:10, 14 Mar 2005 (UTC)
- Yea, there are thousands of text editors out there that have a website; why is this one so relevant? Lost Goblin
Small Correction
The table shows that EditPlus does not support regex find/replace. That is false. I use that feature in EditPlus practically every day.
Add an indication for feature available through plugins, scripts?
I just added jEdit to the comparison, but found that for most options were i had to say 'no' there is a plugin available. This is because jEdit is built to provide only core functionality, which can be expanded by plugin, much like Firefox. Adding an indication like Yes* or Plugin (and/or Script, Macro) for options that are available through plugins,scripts or macro's would give a lot more information i guess
- Add it as footnote then. For example, see comparison of web browsers. --minghong 11:13, 13 Apr 2005 (UTC)
Nano
Edited to reflect the fact that nano does support newline conversion and all three newline types.
scriptable?
I'm surprised that in all this, no reference has been made to the text editors scriptability. I'm not even sure if there is a 'rigorous' definition for scriptability (which is why I thought I should discuss this before editing the page).
I know that if i want vim or emacs to do something that it doesn't already do, I can usually script it, either via lisp (with emacs) or a vim file (with vim). are those the only two editors that offer such features? I'm not sure... I do know that I've saved a lot of time through vim scripts, and I feel like a comparison of text editors just isn't complete unless the issue is brought up. any thoughts?
big table
as there is a Periodic table (huge) set apart from the main article with a warning that it is huge, maybe we could combine all these little tables into one single table (behind a size warning) so people can actually compare them. - Omegatron 21:47, May 26, 2005 (UTC)
plugins
jedit does have spell checking, but it's a plugin. how should we indicate this? - Omegatron 01:29, May 27, 2005 (UTC)
- it is indicated (sort of). it says 'This table lists common basic features supported natively (i.e. without third-party add-ons)'. Plugins don't fall into that category, as far as I know - which is why it's marked as not having a spellchecker. the same is true for vim, and probably most of the other text editors being compared.