all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gnu_lists@halloleo.hailmail.net
Cc: rpluim@gmail.com, 32032@debbugs.gnu.org
Subject: bug#32032: 26.1; Emacs 26 opens under X with blank window
Date: Fri, 06 Jul 2018 15:51:26 +0300	[thread overview]
Message-ID: <83lgaole7l.fsf@gnu.org> (raw)
In-Reply-To: <5E9BAFF1-1EAE-47CD-8983-6B36AB232B9C@hailmail.net> (gnu_lists@halloleo.hailmail.net)

> From: gnu_lists@halloleo.hailmail.net
> Cc: gnu_lists@halloleo.hailmail.net, rpluim@gmail.com, 32032@debbugs.gnu.org
> Date: Fri, 06 Jul 2018 22:33:05 +1000
> 
> 
> [1:text/plain Show]
> 
> 
> [2:text/html Hide Save:noname (2kB)]
> 
>  Given that there are known bugs with this feature that no one is
>  working on, perhaps we should introduce an optional configure switch
>  to build without double-buffering.
> 
>  Agreed. Does it make sense for a Emacs source code newbie to chip in here?
> 
>  Of course.  We were all newbies at some point.
> 
> I created a new `configure.ac` (see https://gist.github.com/halloleo/8f4ba4b1ffcc3874a2ee0e16e03f6618)
> which provides a `--without-backbuffer` option:
> 
>     ./configure --without-gnutls --without-backbuffer

Thanks.

> then builds an Emacs exe which starts up properly on unbuffered X servers without any custom `.emacs` file.
> 
> Where do I put the `configure.ac` file and how do I create a pull request for it?

We don't (yet) work with pull requests.  Please make the change in
your local clone of the Emacs repository, on the master branch, and
then use "git format-patch" to prepare a patch and post the patch
here.

(Please consult CONTRIBUTE in the repository for some of the practices
we advise to use with contributed code.)





  parent reply	other threads:[~2018-07-06 12:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  1:52 bug#32032: 26.1; Emacs 26 opens under X with blank window gnu_lists
2018-07-02 14:35 ` Eli Zaretskii
2018-07-03  7:20   ` gnu_lists
2018-07-03  9:20     ` Robert Pluim
2018-07-03 18:53       ` Eli Zaretskii
2018-07-03 22:57         ` gnu_lists
2018-07-04  2:35           ` Eli Zaretskii
2018-07-06 12:33             ` gnu_lists
2018-07-06 12:50               ` Robert Pluim
2018-07-06 13:20                 ` Eli Zaretskii
2018-07-06 13:54                   ` gnu_lists
2018-07-06 14:04                     ` Robert Pluim
2018-07-06 14:07                     ` Noam Postavsky
2018-07-06 14:57                       ` Robert Pluim
2018-07-06 22:43                         ` gnu_lists
2018-07-06 14:08                     ` Eli Zaretskii
2018-07-06 22:44                       ` gnu_lists
2018-07-07  7:18                         ` Eli Zaretskii
2018-07-06 12:51               ` Eli Zaretskii [this message]
2018-07-06 12:55                 ` Robert Pluim
2018-07-06 13:30                   ` Eli Zaretskii
2018-07-14 23:55                     ` Noam Postavsky
2018-07-15 11:35                       ` Robert Pluim
2018-07-20  9:17                       ` Eli Zaretskii
2018-07-20 12:50                         ` Noam Postavsky
2018-07-21 10:50                           ` Eli Zaretskii
2018-07-21 11:25                             ` leo
2018-07-21 17:20                               ` Robert Pluim
2020-08-26 13:05                             ` Lars Ingebrigtsen
2018-07-06 13:12                 ` gnu_lists
2018-07-08 23:30                 ` leo

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=83lgaole7l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32032@debbugs.gnu.org \
    --cc=gnu_lists@halloleo.hailmail.net \
    --cc=rpluim@gmail.com \
    /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.