From: captain.deadly@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: emacs alternative?
Date: Fri, 5 Nov 2010 09:05:35 +0000 [thread overview]
Message-ID: <201011050905.35358.captain.deadly@gmail.com> (raw)
In-Reply-To: <20101105074341.GK3440@jama>
On Friday 05 November 2010 07:44:09 Martin Jansa wrote:
> On Fri, Nov 05, 2010 at 07:35:25AM +0000, captain.deadly@gmail.com wrote:
> > I posted here before to say that emacs in OE doesn't build on my machine
> > as the Makefile's being generated by autotools are being corrupted
> > somehow. I've not been able to get to the bottom of it at all.
>
> http://article.gmane.org/gmane.comp.handhelds.shr.devel/3131/match=mg
>
> and
>
> emacs-x11_23.1.bb builds in SHR feeds just fine (so you can look there
> for patches needed by emacs_22.3 - probably
> emacs-x11-23.1/configure.in.lost.backslashes.patch).
>
> Regards,
Thanks for that I was trying to build the plain emacs without x and having
those problems. x11 version does work so thanks for the pointer.
next prev parent reply other threads:[~2010-11-05 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 7:35 emacs alternative? captain.deadly
2010-11-05 7:44 ` Martin Jansa
2010-11-05 9:05 ` captain.deadly [this message]
2010-11-05 13:08 ` Mike Westerhof
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=201011050905.35358.captain.deadly@gmail.com \
--to=captain.deadly@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 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.