unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: 21077@debbugs.gnu.org
Subject: bug#21077: 24.5; Slow printing in inferior python buffer with python-shell-enable-font-lock
Date: Fri, 17 Jul 2015 10:56:05 +0200	[thread overview]
Message-ID: <87d1zrkvru.fsf@gmx.us> (raw)
In-Reply-To: <CA+vqiLGTwe4b+O-1iuiyAwM4W59--V5qjEcmPTkTfsnb4xTvSQ@mail.gmail.com>

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> It wasn't.  Something is clearly wrong with the regexps involved in
>> this recipe, at least.
>
> The trigger is simple and a well-known problem in Emacs: the command you
> pass to Python outputs one very long line, and Emacs assumes at various places
> that lines aren't too long.  One such assumption is in font-lock itself,
> another appears to be in one of the regexps used in the font-lock config
> of inferior python mode.

The problem is also very much present in the R interface provided by ESS.

The R package data.table has a pretty good solution to long output IMO.
E.g.

R> data.table(x=1:1000000)
                x
       1:       1
       2:       2
       3:       3
       4:       4
       5:       5
      ---        
  999996:  999996
  999997:  999997
  999998:  999998
  999999:  999999
 1000000: 1000000

As I remember Python Pandas does something similar.

Would it be feasible to implement a generalized version of cutting output
for comint-like output if exceeding N lines?

Rasmus

-- 
Warning: Everything saved will be lost






  reply	other threads:[~2015-07-17  8:56 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
2015-07-17  6:53         ` Eli Zaretskii
2015-07-17  8:33           ` Stefan Monnier
2015-07-17  8:56             ` Rasmus [this message]
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=87d1zrkvru.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=21077@debbugs.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).