unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: xiaohanyu1988@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Need help for oh-my-emacs.
Date: Tue, 15 Oct 2013 18:57:52 -0700 (PDT)	[thread overview]
Message-ID: <466ccb91-a02b-4e77-b44f-265fc4c19453@googlegroups.com> (raw)
In-Reply-To: <87r4bmck35.fsf@nl106-137-194.student.uu.se>

On Wednesday, October 16, 2013 5:14:29 AM UTC+8, Emanuel Berg wrote:
> Xiao Hanyu <xiaohanyu1988@gmail.com> writes:
> 
> 
> 
> > Recently, I'm doing a project
> 
> > https://github.com/xiaohanyu/oh-my-emacs, which aims
> 
> > to be a
> 
> > oh-my-zsh(https://github.com/robbyrussell/oh-my-zsh)
> 
> > for Emacs world.
> 
> 
> 
> I don't get any of this, what did you do?!
> 
> 
> 
> A tool to share/synchronize configuration?
> 
> 
> 
> Isn't there the EmacsWiki for that?
> 
> 
> 
> People just need to share their Elisp, that's the bottom
> 
> line. But people don't like that. That's cheating, they
> 
> think. The proper way is to share references to the
> 
> documentation. Ha ha ha! It is funny because it is
> 
> true. Or "sad", I should say.
> 
> 

To tell the truth, I think some code snippets from emacswiki or blogs or google is not portable and newbie-friendly. Various elisp code from the web conflicts with each other. 
> 
> Sorry, can you just describe the project, more in terms
> 
> of your idea, its goal, etc., and perhaps share some
> 
> screenshots, rather than in terms of the scope of the
> 
> project, etc.?
> 
> 

Hi, I've already write lots of docs about what this project is and its goal, please try to read its readme file: https://github.com/xiaohanyu/oh-my-emacs/blob/master/README.org .

> 
> > 1. A literate way to keep code and documentation
> 
> > synced, thus get rid of outdated elisp code snippets
> 
> > from google or emacs blogs.  2. Use el-get to manager
> 
> > packages, no need to manage load-path and info doc
> 
> > 3. Self adapted, only install necessary packages when
> 
> > it satisfies the prerequisites.
> 
> 
> 
> OK, so it is a *package manager*, like aptitude or
> 
> apt-get for Debian and the like? Is that really better
> 
> than to just share Elisp?
> 
> 
Definitely sure, a package manager is much more better than sharing code in emacswiki or some other places. Here's some references: https://github.com/xiaohanyu/oh-my-emacs/blob/master/ome.org#package-management .

> 
> > 4. better default settings, lots of eye candy.
> 
> 
> 
> Well... people have different taste. I like Emacs to
> 
> look like a CRT, others like it to look like a book from
> 
> some French fashion publisher... Perhaps we should leave
> 
> that to each, as we will never reach a conclusion, and
> 
> if we try, there will only be bad blood. (This is about
> 
> Emacs. Maybe you referred you your tool? Is that a
> 
> standalone tool or some Emacs mode by the way?)
> 
> 

I know that, so I just provide modules, you can make your own choices.

> 
> > 3. develop new modules for languages that I have no
> 
> > idea of, such as erlang/haskell.
> 
> 
> 
> I did work in both of those languages and there are
> 
> Emacs modes for them. Why would you want new modules?
> 
> 

Emacs already has lots of builtin mode, so why there comes lots of third-party packages such as js2-mode, elpy, SLIME, nrepl? Since the builtin mode is not powerful, we need third party packages.

> 
> > When things goes well, I'll try to make an official
> 
> > emacs distribution for out-of-box use, see
> 
> > https://github.com/xiaohanyu/oh-my-emacs/issues/16.
> 
> 
> 
> OK, I hate to be a jerk, but
> 
> 
> 
> 1. What problems did you experience with the
> 
> "distribution" of Emacs that you used, prior to
> 
> undertaking this project?
> 
> 
> 
> and
> 
> 
> 
> 2. What made you think that the solution was in a *new*
> 
> distribution, rather than solving the problem *where you
> 
> found it*?
> 
> 

Nobody want to work with plain emacs. oh-my-emacs just provide a basic point. Just like no body want to work with plain linux kernel, so there comes Ubuntu/Gentoo/Archlinux etc. 

> 
> > The current oh-my-emacs contains 1. about 900 lines of
> 
> > emacs lisp code 2. about 3500 lines of documentation.
> 
> > 3. about 50 powerful el-get packages.
> 
> 
> 
> In three months, you seemed to have worked very, very
> 
> hard on this project. I hope (no irony) you have good
> 
> answers to my questions, but even if you don't, no one
> 
> can take away your work habits and dedication.
> 
> 
> 
> PS. Again, *screenshots* would clarify a lot! DS.
> 
> 
Some screenshots: http://www.douban.com/photos/album/117065634/.
> 
> -- 
> 
> Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
> 
> underground experts united:  http://user.it.uu.se/~embe8573


  reply	other threads:[~2013-10-16  1:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4020.1381818436.10748.help-gnu-emacs@gnu.org>
2013-10-15 21:14 ` Need help for oh-my-emacs Emanuel Berg
2013-10-16  1:57   ` xiaohanyu1988 [this message]
2013-10-16  2:17     ` Emanuel Berg
2013-10-16  2:35       ` Emanuel Berg
2013-10-16  2:52         ` xiaohanyu1988
2013-10-17  0:38           ` Emanuel Berg
2013-10-15  6:14 Xiao Hanyu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=466ccb91-a02b-4e77-b44f-265fc4c19453@googlegroups.com \
    --to=xiaohanyu1988@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).