From: Andrew Hyatt <ahyatt@gmail.com>
To: Markus Triska <markus.triska@gmx.at>,
Ivan Andrus <darthandrus@gmail.com>
Cc: 1148@debbugs.gnu.org
Subject: bug#1148: 23.0.60; recursive edits can sometimes not be stopped in emacsclient
Date: Thu, 07 Jan 2016 03:44:12 +0000 [thread overview]
Message-ID: <CAM6wYY+xxjrDS_WfhD34RFpNvj+MAdKhZQ43JfP6tjZEO+DeqQ@mail.gmail.com> (raw)
In-Reply-To: <trinity-ae49f275-ae0c-43dd-ac45-fa2a56a83ffa-1452018960357@3capp-gmx-bs50>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Tue, Jan 5, 2016 at 1:36 PM Markus Triska <markus.triska@gmx.at> wrote:
> Hi Ivan,
>
> Ivan Andrus writes:
>
> > That bug (#1504) has been closed, so if it still leaks memory you
> > should open a new bug (or reopen that one).
>
> #1504 contains all the information for reproducing the problem, and
> you can easily see that the problem still exists in the latest git
> version of Emacs.
>
> If possible, I would like to focus on filing the issues I find and
> providing you with all the information you need to reproduce these
> problems, so please classify the issues I file as you see fit.
>
> Thank you and all the best!
> Markus
>
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.
[-- Attachment #2: Type: text/html, Size: 1277 bytes --]
next prev parent reply other threads:[~2016-01-07 3:44 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 [this message]
2016-01-08 18:15 ` Markus Triska
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=CAM6wYY+xxjrDS_WfhD34RFpNvj+MAdKhZQ43JfP6tjZEO+DeqQ@mail.gmail.com \
--to=ahyatt@gmail.com \
--cc=1148@debbugs.gnu.org \
--cc=darthandrus@gmail.com \
--cc=markus.triska@gmx.at \
/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.