unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Building Emacs on WSL
Date: Tue, 20 Dec 2016 23:01:59 +0100	[thread overview]
Message-ID: <CAFgFV9OzrzKPqtJL85HDSgj-AmYTuA6Jx7T88H78Q4OTUW8r8Q@mail.gmail.com> (raw)
In-Reply-To: <91754a74-f739-84c2-62be-34f702000292@alice.it>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

2016-12-20 22:19 GMT+01:00 Angelo Graziosi <angelo.graziosi@alice.it>:

> Il 20/12/2016 13:20, Fabrice Popineau ha scritto:
>
>> For the record,
>>
>> Emacs 25.1 builds fine and runs fine under WSL providing you install all
>> the required packages.
>> I used :
>>  ../emacs/configure --with-jpeg --with-xpm --with-tiff --with-rsvg
>> --with-xml2 --with-gnutls --with-imagemagick --with-png=yes
>> and mobaxterm as an X server. Everything is ok. I could even load
>> Spacemacs
>> with its about 100 packages.
>>
>>
> Yes, emacs-25 branch builds (adopting the work around 'echo 0 | sudo tee
> /proc/sys/kernel/randomize_va_space' before to start the build) but I do
> not use these builds in X,
>
> $ /opt/emacs/bin/emacs
>
> starts Emacs in the WSL terminal (aka DOS command prompt window in W10).
> It seems to work fine.. but have found an issue with the packages manager.
> See: http://lists.gnu.org/archive/html/bug-gnu-emacs/2016-12/msg00777.html
> .
>
> Have you tried to use your builds in terminal mode (noX)?
>
>
The problem seems to be with running emacs in the console.
It is working as expected in GUI mode, but in the the terminal, it is
suspended every key I type.

Fabrice

[-- Attachment #2: Type: text/html, Size: 1940 bytes --]

      reply	other threads:[~2016-12-20 22:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 17:42 Building Emacs on WSL Angelo Graziosi
2016-12-16 15:05 ` Angelo Graziosi
2016-12-16 15:30   ` Eli Zaretskii
2016-12-16 17:48     ` Paul Eggert
2016-12-16 21:05       ` Eli Zaretskii
2016-12-17  1:00         ` Angelo Graziosi
2016-12-17  8:02           ` Eli Zaretskii
2016-12-17  8:33             ` Angelo Graziosi
2016-12-17 10:55               ` Eli Zaretskii
2016-12-17 14:25           ` Eli Zaretskii
2016-12-17 15:46             ` Angelo Graziosi
2016-12-20 12:20   ` Fabrice Popineau
2016-12-20 12:40     ` Fabrice Popineau
2016-12-20 19:35       ` Paul Eggert
2016-12-20 20:03         ` Fabrice Popineau
2016-12-20 23:59           ` Angelo Graziosi
2016-12-21  3:20           ` Paul Eggert
2016-12-21  8:54             ` Angelo Graziosi
2016-12-21 18:00               ` Paul Eggert
2016-12-21 20:50                 ` Angelo Graziosi
2016-12-20 20:57         ` Angelo Graziosi
2016-12-21  9:00       ` Angelo Graziosi
2016-12-21 10:29         ` Fabrice Popineau
2016-12-20 21:19     ` Angelo Graziosi
2016-12-20 22:01       ` Fabrice Popineau [this message]

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=CAFgFV9OzrzKPqtJL85HDSgj-AmYTuA6Jx7T88H78Q4OTUW8r8Q@mail.gmail.com \
    --to=fabrice.popineau@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=emacs-devel@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 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).