unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: running ./temacs
Date: Tue, 31 May 2011 02:55:23 -0400	[thread overview]
Message-ID: <yxqvcwrz7dw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1QRIju-0004kg-U0@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 31 May 2011 02:47:42 -0400")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Dan Nicolaescu <dann@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
>> Date: Tue, 31 May 2011 02:36:38 -0400
>> 
>> It looks like this is enough to get ./temacs run in X11 mode:
>> 
>> === modified file 'src/dispnew.c'
>> --- src/dispnew.c 2011-05-25 03:45:04 +0000
>> +++ src/dispnew.c 2011-05-31 06:17:37 +0000
>> @@ -6235,9 +6235,6 @@ init_display (void)
>>      }
>>  
>>    if (!inhibit_window_system && display_arg
>> -#ifndef CANNOT_DUMP
>> -     && initialized
>> -#endif
>>       )
>>      {
>>        Vinitial_window_system = Qx;
>> 
>> === modified file 'src/frame.c'
>> --- src/frame.c   2011-05-29 00:45:00 +0000
>> +++ src/frame.c   2011-05-31 06:13:37 +0000
>> @@ -544,10 +544,8 @@ make_initial_frame (void)
>>    /* The default value of menu-bar-mode is t.  */
>>    set_menu_bar_lines (f, make_number (1), Qnil);
>>  
>> -#ifdef CANNOT_DUMP
>>    if (!noninteractive)
>>      init_frame_faces (f);
>> -#endif
>>  
>>    return f;
>>  }
>> 
>> Any reason not to check this in?
>
> What would be the purpose of getting temacs run in GUI mode?

Minimize the differences between temacs and emacs.  Other than dumping,
is it useful to have temacs and emacs behave differently?

Hopefully temacs should be much easier to get to work under valgrind
(and other similar tools) for example.
Another use would be for cross-compiling.  One can cross-compile temacs,
but if the result behave differently, it's not very useful.  If it
behaved the same, it would start up slower, but it would otherwise work
just the same as emacs.



  reply	other threads:[~2011-05-31  6:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  6:57 running ./temacs Dan Nicolaescu
2010-11-17  7:43 ` Óscar Fuentes
2010-11-18  4:44 ` Dan Nicolaescu
2010-11-18 14:26   ` Stefan Monnier
2010-11-18 21:20     ` Dan Nicolaescu
2010-11-18 22:17       ` Stefan Monnier
2010-11-18 22:19         ` Dan Nicolaescu
2010-11-19  7:51           ` Eli Zaretskii
2010-11-20  7:28             ` Dan Nicolaescu
2010-11-21  5:48             ` Stefan Monnier
2011-05-31  5:19               ` Dan Nicolaescu
2011-05-31  6:36                 ` Dan Nicolaescu
2011-05-31  6:47                   ` Eli Zaretskii
2011-05-31  6:55                     ` Dan Nicolaescu [this message]
2011-05-31  8:44                       ` Eli Zaretskii
2011-05-31 14:53                         ` Dan Nicolaescu
2011-05-31  6:40                 ` Eli Zaretskii

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=yxqvcwrz7dw.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).