After A Year, Emacswiki Alternative Shutting Down
About a year ago, someone decided that EmacsWiki was outdated and unorganized, to the detriment of the Emacs community. So, he started a new wiki (WikiEmacs, choosing Mediawiki instead of Oddmuse, and attempting to give it a saner organizational structure). In the end, his project failed to grain traction, and it's shutting down for the greater good of Emacs: "I want to extend a big public apology to Alex Schroeder for my harsh criticism of EmacsWiki. One year later I see that stewarding documentation projects and nurturing a healthy community around them is much harder than writing software. I’m but a humble software engineer and you’ll have to forgive me for my misguided actions. I hope that something good has(will) come up from all this drama. At the very least I urge everyone who cares for EmacsWiki to try and clean up, extend and improve at least a couple of articles on subjects that are of importance to him. I know that’s something I’ll be doing from now on."
Is this serious? Its a fscking editor for gods sake. Is there a "vi community"? Who the hell cares enough to even bother? Or perhaps I'm misguided and there are thousands of people out there who find editors the most fascinating programs ever written. Is there an "ls" or "rm" community just out of interest?
ok now i feel better..
i hate missing parantheses!
Shutting down in less than a year because the project got too little attention is foolish as it takes years for most users to discover you. I had no idea it existed, if I knew, I would have tried it as I do believe that EmacsWiki has a fair amount of problems. Shutting down and dragging down all content and time that users were willing to contribute is just ridiculously irresponsible. EmacsWiki may not be perfect, but it has been around for years and I am fairly confident that the owner will not decide to shut it down tomorrow or next year on a whim like this guy.
Really? I thought it was Lynx.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
Don't be so harsh. It's perfectly reasonable to shut down a project if it doesn't succeed on the schedule the organizer wants. It would be more foolish to continue to invest in the forked project after realizing it was a mistake at the outset.
[Sir Garlon] is the marvellest knight that is now living, for he destroyeth many good knights, for he goeth invisible.
I'm not shutting down the project on a whim, a lot of thought and discussions with members of Emacs community are involved in it. The content will be preserved on EmacsWiki and I'll continue to work with Alex and the other members of the EmacsWiki team to (hopefully) improve and clean it up.
Because there is a nice integration between the other buffers and your terminals. For example, say that you want to run a few commands in the same directory that the file you are editing exists. In that case you just type M-x shell to start a shell in that directory. (Note that this also works if you are working with a file on another computer via ssh. Your shell will then automatically start over an ssh session.)
If you are running commands that outputs a lot of text in the terminal the search capability of emacs is really useful as well.
Another use case is the integration between macros, text buffers, and terminals. Consider a use case where you are editing an HTML file and want to ensure that all images referred to in IMG tags are available at a remote location. It is then easy to create a macro in emacs that finds all IMG tags, extract the file name and copy the file name to a suitable scp command that you can paste into the terminal window.
However, I must admit that I still have a few xterms open, but I find myself gravitating towards running shell commands in a shell buffer in emacs, especially when programming. Also, there are of course other ways to solve all of these issues (scripting, file redirection, etc), but for myself I usually find myself preferring to use emacs in most of these cases.
I dug more deeply into your posts and see now that you planned your wiki as a temporal experiment from the very beginning (and quite explicitly said so). It's great that you intend to preserve the user-created data as well, so nothing of value will be lost. Still, I think your project would have grown much more popular in a few years if you didn't give up and gave some sort of a pledge that it won't be shut down in a year or two. Anyway, thank you for your attempt in improving this valuable source of information.
Well what kind of organization did you expect from people who came up with 17 different kinds of keyboard shift keys?
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
...is the decision to go with MW. Seriously. Look at WikiEmacs, then at EmacsWiki. The main problem with WikiEmacs (the MW version) is that you are forced to read the content in order to find what it is you need. Compare that to EmacsWiki: Links are clearly defined, not embedded in a lot of cruft, and describe exactly what it is that the link points to.
I've said this before: MW is overbloated and has a horrible UI, to the point where navigating most MW sites are excruciatingly painful. Anyone who thinks that MW is actually a user-friendly experience that promotes quick and easy navigation and drill-down is obviously a glutton for punishment and knows nothing about proper UI design.