Re: [E-devel] e16menuedit2 - documentation?
Am Thu, 5 Aug 2004 23:58:28 +0200 schrieb Andreas Volz: I'm still not sure how to create the documentation. Currently I prefer yelp (gnome-help) for it. And then for people without Gnome convert all to HTML and invoke a browser to view the help. If you've a better idea how to create user docs say it before I start. Another question. Do E related projects use a special documentation licence? I don't know if BSD style licence covers also documentation? If not I choose the GNU Free Documentation License (GFDL). Andreas --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Time to get started.
On Fri, 06 Aug 2004 10:17:19 +1000, Nick Blievers said: I dont disagree that a simple GUI editor should be the default but lets do it the Unix way, and have an EDITOR variable set. Else we end up with yet another way of setting the default editor. This loses big time for those people who have EDITOR set to something that will DTRT when invoked in any sort of vt-100 emulator (everything from a Linux console to a telnet/ssh to an xterm). The Unix Way has long assumed that using your shell's version of 'export EDITOR=/usr/bin/vi' will do something reasonable. And in fact, that's quite sane until some application decides that $EDITOR is presumed to be smart enough to open an X window all by itself, without a 'FooTerm -e $EDITOR $*' wrapper to do the windowing stuff for it. Using $XEDITOR instead, to denote a GUI-aware editor, might be a good idea pgpoY2CtbluFt.pgp Description: PGP signature
