From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Building Emacs on WSL
Date: Sat, 17 Dec 2016 02:00:31 +0100 [thread overview]
Message-ID: <67607fa7-0e19-a371-4df4-f37af436213e@alice.it> (raw)
In-Reply-To: <83zijv7ff6.fsf@gnu.org>
Hi BIGS...
Il 16/12/2016 22:05, Eli Zaretskii ha scritto:
>> Cc:
>> From: Paul Eggert
>> Date: Fri, 16 Dec 2016 09:48:35 -0800
>>
>> Eli Zaretskii wrote:
>>> If you want this issue solved, please attach a debugger to temacs, and
>>> post the backtrace, preferably after filing a bug report.
>>
>> I thought the goal was to get portable dumping working soon? If so, this problem
>> with WSL ought to be low priority, as portable dumping will make this porting
>> problem irrelevant.
>
> We don't know yet what caused this problem. And I don't think future
> developments should prevent users from reporting bugs. We can, of
> course, decide not to fix this or that bug, but I don't think we
> should tell users we don't want to hear about them.
>
I understand this is a low priority issue if it is... Remember that WSL
is marked as "beta". I flagged this only for the record, just in case
someone had a similar experience.
BTW, in my builds of emacs-25 branch I notice a more serious issue.
After "M-x package-list-packages", in the Packages buffer I cannot type
anything. If I do, I get, embedded in that buffer,
[1]+ Stopped
and the Bash prompt, as if I had typed C-z, and 'fg' seems partially
resurrect Emacs, but it is unusable. I have to close WSL window. In
short I cannot install packages from MELPA/ELPA with these builds.
This issue is absent if I install (in WSL) the Ubuntu package
emacs24-nox with apt-get...
I did also a build of emacs-25 using more or less the same "configure"
with which emacs24-nox is built in Ubuntu. But no good results.
Ciao,
Angelo.
next prev parent reply other threads:[~2016-12-17 1:00 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 [this message]
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
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=67607fa7-0e19-a371-4df4-f37af436213e@alice.it \
--to=angelo.graziosi@alice.it \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).