On 21/08/16 23:03, Ken Brown wrote:
OK, let's wait to hear from Volker (or maybe Yaakov has some insight?).
BTW, I've looked at the sources for gd-2.2.3-1, and the string
"WebPDecode" appears only once, in a call to WebPDecodeARGB. So I
don't understand why there wasn't an ABI bump between ve
Hi all,
When I type 'emacs' at the bash prompt, emacs does not start and the
prompt re-appears very quickly as if nothing happened. 'emacs -Q' and
'emacs --version' do the same, nothing is printed.
My alternatives are set such that emacs points to emacs-w32. I also have
emacs-nox and that wo
On Fri, Mar 20, 2015 at 9:56 PM, Yaakov Selkowitz wrote:
> On Fri, 2015-03-20 at 15:03 +0000, Peter Hull wrote:
>> Is this expected/normal or have I done something wrong?
> This is not expected. Nothing depends on epiphany that would have
> caused it to be pulled in without hav
I just ran setup (2.870, 32-bit) and it installed a lot of GNOME
software that I didn't have before and didn't ask for(e.g. Epiphany).
My fault for clicking through I suppose without checking.
Looking at dependencies in setup.ini I see xinit requires
adwaita-icon-theme and that pulls in a load of
On Fri, Feb 13, 2015 at 10:59 AM, Adam Dinwoodie wrote:
> I'm running a bunch of Microsoft Office applications which I know do
> "helpful" things to the Windows clipboard. It hadn't occured to me that
> they may be causing BLODA-like problems in the way they interact with
> it.
Just to add my exp
On Wed, Dec 10, 2014 at 1:00 PM, Ken Brown wrote:
> Fork errors often indicate a need to run rebaseall. Have you tried that?
That fixed it, thanks Ken.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com
When I start emacs 24.4.1 I see a message in the console:
** (emacs:8264): WARNING **: Error retrieving accessibility bus
address: org.a11y.Bus.Error: Failed to fork (Resource temporarily
unavailable)
This does not seem to cause any problem that I have seen but it only
started appearing recently (I
On Mon, Sep 22, 2014 at 3:21 PM, Doug Lewan wrote:
> The announcement below (re: pretest of emacs 24.4) is starting to confuse me.
I see the same as you. Also, in setup-x86.exe I see "24.3.93-1 Keep"
but I can press the cycle thing and get the option of 24.3.93-3. Do
you see that? It may be becaus
On Mon, Aug 25, 2014 at 8:00 PM, Ken Brown wrote:
> It looks like my idea is going to work, but it needs testing to make sure
> I've implemented it correctly. If anyone is willing to test it, you can
> download emacs-24.3.93-2 from my personal Cygwin repository:
I've downloaded it - no problems s
On Thu, Aug 21, 2014 at 6:08 AM, Achim Gratz wrote:
> Ken Brown writes:
>> This is another pretest of the upcoming emacs-24.4, replacing the
>> current pretest (24.3.91-1). It includes a workaround for the bug
>> reported in
It seems to have fixed my original problem with vc integration though
I
On Mon, Aug 18, 2014 at 1:28 PM, Ken Brown wrote:
> I've just made a new emacs test release that includes a workaround for this
> bug. I think I see a way to make emacs use Cygwin's malloc; if this works,
> it will provide a better fix for the bug.
I'd like to give this a try. I've selected Exp m
A bug in Emacs? Gosh I thought it was probably just me doing something silly!
Thanks for your help everyone in tracking this down.
Ken, do you know if it's possible to subscribe to the bug report - I'd
be interested in knowing how it pans out.
Pete
--
Problem reports: http://cygwin.com/pr
In my experiments, not calling pthread_mutexattr_init caused errors
such that the final mutex was invalid and could not be locked.
The difference between the explicitly initialised mutex and the
statically initialised one is that the latter does get 'lazily'
initialised when the mutex is first loc
On Tue, Aug 5, 2014 at 1:21 PM, Ken Brown wrote:
> - pthread_mutex_init (&_malloc_mutex, NULL);
> - pthread_mutex_init (&_aligned_blocks_mutex, NULL);
> + pthread_mutexattr_t attr1, attr2;
> + pthread_mutexattr_settype (&attr1, PTHREAD_MUTEX_NORMAL);
> + pthread_mutexattr_settype (&attr2, PTH
On Mon, Aug 4, 2014 at 2:02 AM, Ken Brown wrote:
> That does seem to be the problem, since I can reproduce the bug starting
> with the 2014-07-14 snapshot. More precisely, I can reproduce it using
> emacs-nox (which is what the OP was using according to his cygcheck output)
> but not using emacs-
On Fri, Aug 1, 2014 at 1:50 PM, Angelo Graziosi
wrote:
> Since I upgraded to Cygwin-1.7.31*, I see similar issue in building Emacs
> trunk (--with-w32 build)... The build always hangs in compiling some .el
> file. CTRL-C does not work and I have to search the running processes with
> "ps" and kill
On Fri, Aug 1, 2014 at 11:22 AM, Katsumi Yamaoka wrote:
> On Thu, 31 Jul 2014 15:51:49 +0100, Peter Hull wrote:
> I'm troubled with a similar problem since Wednesday[1].
I checked my /var/log/setup.log. The last time I installed anything
was 2014/07/30 (Wednesday). That update i
>I can't reproduce this. I tested both emacs-X11 and emacs-w32, on both
>32-bit Cygwin and 64-bit Cygwin. Can you think of anything on your
>system that has changed in the last few days? And have you tried
>starting emacs with the '-Q' option to rule out a problem in your
>initialization files?
VC integration in emacs has stopped working for me in the past few
days. Using emacs debugger I found the last function call was to
call-process which never returns.
I can reproduce this by evaluating in Lisp Interaction mode (using ^J)
(call-process "pwd" nil t)
I would expect to see the PWD and
19 matches
Mail list logo
