all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Markus Triska" <markus.triska@gmx.at>
To: "Andrew Hyatt" <ahyatt@gmail.com>
Cc: Ivan Andrus <darthandrus@gmail.com>, 1148@debbugs.gnu.org
Subject: bug#1148: 23.0.60; recursive edits can sometimes not be stopped in emacsclient
Date: Fri, 8 Jan 2016 19:15:31 +0100	[thread overview]
Message-ID: <trinity-60968416-abc8-40b0-a753-ebc86a2d19ce-1452276930951@3capp-gmx-bs31> (raw)
In-Reply-To: <CAM6wYY+xxjrDS_WfhD34RFpNvj+MAdKhZQ43JfP6tjZEO+DeqQ@mail.gmail.com>

Hi Andrew,
 
Andrew Hyatt writes: 

> FWIW, I can't reproduce that bug on my Mac.  Or, if it leaks memory, it
> leaks it so slowly that even running the emacsclient loop for minutes
> results in no clear difference.  It may be that there is some system level
> difference, or difference in how we built or installed emacs that's causing the issue.

Here are the settings I use on OSX 10.10.2, and which allow me to reproduce #1504
with the latest git version today: 

 ./configure --without-ns CFLAGS=-I/opt/local/include LDFLAGS=-L/opt/local/lib

and the following features (note in particular X11 and LUCID):

XAW3D XPM JPEG TIFF GIF PNG IMAGEMAGICK GSETTINGS NOTIFY ACL GNUTLS
LIBXML2 FREETYPE XFT ZLIB TOOLKIT_SCROLL_BARS LUCID X11

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix





  reply	other threads:[~2016-01-08 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 15:43 bug#1148: 23.0.60; recursive edits can sometimes not be stopped in emacsclient Markus Triska
2016-01-04  0:34 ` Andrew Hyatt
2016-01-04 20:04   ` Markus Triska
2016-01-05  3:59     ` Andrew Hyatt
2016-01-05  4:47     ` Ivan Andrus
2016-01-05 18:36       ` Markus Triska
2016-01-07  3:44         ` Andrew Hyatt
2016-01-08 18:15           ` Markus Triska [this message]
2016-01-24 21:24             ` Andrew Hyatt

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=trinity-60968416-abc8-40b0-a753-ebc86a2d19ce-1452276930951@3capp-gmx-bs31 \
    --to=markus.triska@gmx.at \
    --cc=1148@debbugs.gnu.org \
    --cc=ahyatt@gmail.com \
    --cc=darthandrus@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.