From: xiaohanyu1988@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: Need help for oh-my-emacs.
Date: Tue, 15 Oct 2013 19:52:08 -0700 (PDT) [thread overview]
Message-ID: <9cbdc768-4c7f-4dd3-97f6-d0bb2a44ca3b@googlegroups.com> (raw)
In-Reply-To: <8761syaqni.fsf@nl106-137-194.student.uu.se>
On Wednesday, October 16, 2013 10:35:36 AM UTC+8, Emanuel Berg wrote:
> Emanuel Berg <embe8573@student.uu.se> writes:
>
>
>
> > Some screenshots ...
>
> >
>
> > Get back to you...
>
>
>
> OK, I still don't get the basic idea. To have Emacs
>
> fragmented like the Linux distributions is a terrible,
>
> horrible thought. Total fragmentation which amounts to a
>
> change of desktop background color...
>
>
>
> To have one zillion hours of overhead migrating files,
>
> setting up paths, to have a system that is 99% the same,
>
> ... in order to fix a problem that you could have done
>
> with one line in .emacs or .zshrc or .Xresources - the
>
> *same* line, by the way, for all those silly distros! It
>
> just doesn't make any sense to me.
>
>
>
> But let's not argue. Keep it up. I would.
>
>
>
> --
>
> Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
>
> underground experts united: http://user.it.uu.se/~embe8573
Ah, thanks.
Do you know or hear about projects like https://github.com/bbatsov/prelude or https://github.com/eschulte/emacs24-starter-kit, or something similar for vim(http://vim.spf13.com/)? Or you write your own .emacs config from the bottom up line by line?
How do you think about those projects?
next prev parent reply other threads:[~2013-10-16 2:52 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
2013-10-16 2:17 ` Emanuel Berg
2013-10-16 2:35 ` Emanuel Berg
2013-10-16 2:52 ` xiaohanyu1988 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9cbdc768-4c7f-4dd3-97f6-d0bb2a44ca3b@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.