From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Build Emacs without Lisp?
Date: Sun, 26 Jun 2016 05:51:18 -0700 (PDT) [thread overview]
Message-ID: <4d959711-2d1b-49df-bca1-847118bfabbc@googlegroups.com> (raw)
In-Reply-To: <mailman.92.1466943613.26859.help-gnu-emacs@gnu.org>
On Sunday, June 26, 2016 at 5:50:15 PM UTC+5:30, Jeffrey Walton wrote:
> >> My questions are:
> >>
> >> - Is it possible to build emacs without Lisp? If so, how?
> >>
> >> - Are there other work arounds available for the seg fault?
> >>
> >
> > Taking your subject line literally (ie not the usual way its done today
> > to suggest emacs = gnu-emacs)
> > have you seen this list of 'smaller' emacsen: https://en.wikipedia.org/wiki/Emacs#Various_Emacs_editors
>
> Thanks, that's a good point. I'm so used to emacs, I grab it with no thought.
>
> Maybe an emacs knock-off is a better solution until we get a working
> debugger to investigate the issue.
>
My first encounter with emacs was 25 years ago -- jove -- pure C
[Not counting edwin -- pure scheme -- around the same time]
I'd be surprised if that stuff worked today...
IOW How much of that list is current... Dunno
next prev parent reply other threads:[~2016-06-26 12:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.33.1466862026.26859.help-gnu-emacs@gnu.org>
2016-06-25 16:48 ` Build Emacs without Lisp? Emanuel Berg
2016-06-25 17:04 ` Pascal J. Bourguignon
2016-06-25 18:21 ` Emanuel Berg
2016-06-25 20:29 ` Jeffrey Walton
2016-06-26 11:54 ` Rusi
2016-06-26 12:20 ` Jeffrey Walton
2016-06-26 15:14 ` Klaus Schilling
2016-06-26 16:58 ` Phillip Lord
2016-06-26 19:14 ` Jeffrey Walton
2016-06-26 21:17 ` Phillip Lord
2016-06-26 21:34 ` Jeffrey Walton
2016-06-26 22:43 ` Phillip Lord
2016-06-26 22:50 ` Jeffrey Walton
2016-06-27 8:16 ` Phillip Lord
[not found] ` <mailman.160.1467015373.26859.help-gnu-emacs@gnu.org>
2016-06-27 10:16 ` Emanuel Berg
[not found] ` <mailman.131.1466981413.26859.help-gnu-emacs@gnu.org>
2016-06-26 23:25 ` Emanuel Berg
2016-06-26 23:37 ` Jeffrey Walton
[not found] ` <mailman.134.1466984276.26859.help-gnu-emacs@gnu.org>
2016-06-27 4:36 ` Emanuel Berg
2016-06-27 18:19 ` Pascal J. Bourguignon
2016-06-27 18:16 ` Pascal J. Bourguignon
2016-06-27 19:54 ` Emanuel Berg
2016-06-27 18:17 ` Pascal J. Bourguignon
2016-06-28 2:59 ` Dan Espen
[not found] ` <mailman.116.1466968454.26859.help-gnu-emacs@gnu.org>
2016-06-26 19:48 ` Emanuel Berg
2016-06-26 20:11 ` Jeffrey Walton
2016-06-26 20:30 ` Jeffrey Walton
[not found] ` <mailman.121.1466973057.26859.help-gnu-emacs@gnu.org>
2016-06-26 22:26 ` Emanuel Berg
[not found] ` <mailman.120.1466971868.26859.help-gnu-emacs@gnu.org>
2016-06-26 22:22 ` Emanuel Berg
2016-06-26 22:44 ` Jeffrey Walton
2016-06-27 18:12 ` Pascal J. Bourguignon
[not found] ` <mailman.92.1466943613.26859.help-gnu-emacs@gnu.org>
2016-06-26 12:51 ` Rusi [this message]
2016-06-26 18:18 ` Bob Proulx
2016-06-27 18:01 ` Pascal J. Bourguignon
2016-06-27 22:42 ` Gene
2016-06-27 22:54 ` John Mastro
2016-06-27 23:13 ` Stefan Monnier
[not found] ` <mailman.220.1467069232.26859.help-gnu-emacs@gnu.org>
2016-06-28 9:01 ` Emanuel Berg
2016-06-28 19:48 ` klaus schilling
2016-06-27 23:09 ` Bob Proulx
[not found] <mailman.247.1467143377.26859.help-gnu-emacs@gnu.org>
2016-06-28 21:48 ` Emanuel Berg
2016-06-25 7:50 Jeffrey Walton
2016-06-25 20:01 ` Phillip Lord
2016-06-26 13:22 ` Yuri Khan
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=4d959711-2d1b-49df-bca1-847118bfabbc@googlegroups.com \
--to=rustompmody@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).