From: Ista Zahn <istazahn@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21077@debbugs.gnu.org
Subject: bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock
Date: Thu, 16 Jul 2015 15:50:05 -0400 [thread overview]
Message-ID: <CA+vqiLHvxJ0uHHSY1mph7-AK3yh5ATTF=0Lzm+Hrc_oRsWuH+A@mail.gmail.com> (raw)
In-Reply-To: <834ml37v7a.fsf@gnu.org>
On Thu, Jul 16, 2015 at 3:34 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Ista Zahn <istazahn@gmail.com>
>> Date: Thu, 16 Jul 2015 15:09:19 -0400
>> Cc: 21077@debbugs.gnu.org
>>
>> Either way this is not good. Clearly there is something wrong here.
>> Nitpicking about whether it requires killing emacs or not doesn't seem
>> helpful to me.
>
> I thought I was doing fine by providing additional details about the
> problem. Now I'm beginning to think I maybe should have kept my mouth
> shut.
I'm sorry, I came of sounding nasty there. I felt you were minimizing
the seriousness of the issue, which I see now may not have been your
intent. And even if it was there was no reason for me to be so
ill-tempered. So, my apologies.
Best,
Ista
next prev parent reply other threads:[~2015-07-16 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 16:42 bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock Ista Zahn
2015-07-16 18:34 ` Eli Zaretskii
2015-07-16 19:09 ` Ista Zahn
2015-07-16 19:34 ` Eli Zaretskii
2015-07-16 19:50 ` Ista Zahn [this message]
2015-07-17 6:53 ` Eli Zaretskii
2015-07-17 8:33 ` Stefan Monnier
2015-07-17 8:56 ` Rasmus
2015-07-29 20:50 ` Ista Zahn
2015-07-30 23:19 ` Stefan Monnier
2015-07-31 0:27 ` Ista Zahn
2015-07-31 22:07 ` Stefan Monnier
2015-08-01 1:46 ` Ista Zahn
2015-08-01 12:36 ` Wolfgang Jenkner
2015-08-01 16:26 ` Ista Zahn
2015-08-03 23:57 ` Wolfgang Jenkner
2016-07-14 1:31 ` npostavs
2015-08-01 12:42 ` Wolfgang Jenkner
2015-08-03 21:41 ` Stefan Monnier
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='CA+vqiLHvxJ0uHHSY1mph7-AK3yh5ATTF=0Lzm+Hrc_oRsWuH+A@mail.gmail.com' \
--to=istazahn@gmail.com \
--cc=21077@debbugs.gnu.org \
--cc=eliz@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).