edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] master
Date: Wed, 29 Jan 2014 10:48:03 +0000	[thread overview]
Message-ID: <20140129104803.GE7404@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140028164501.eklhad@comcast.net>

On Tue, Jan 28, 2014 at 04:45:01PM -0500, Karl Dahlke wrote:
> Another often requested feature is imap,
> something I've wanted to do for a while.
> Don't know anything about it; I'd have to start with the rfc.
> Or maybe there's an imap library that we could use.
I suspect there's a library we can use for this,
but can't think what it's called.
> 
> > to increase the max limit on the number of lines
> 
> Sounds easy, but the line number is actually sprintfed into places with seven spaces,
> with other characters around it,
> so would take some rewriting to increase it.
> I know, kind of a bad design, but 15 years ago who would imagine
> wanting to store more than 10 million lines??
> I can find the code in buffers.c and point it out,
> or think about what it would take to modify.

Both would be nice. I have to say, until I loaded my first multi-hundred mb
ascii file into edbrowse I'd never thought 10000000 lines was a problem.
> 
> > same for max line length
> 
> You realize that lines are arbitrarily long inside,
> else you could not faithfully download a binary file.
> The line length is just what is displayed,
> and it can be changed by

Yeah, in theory, but I've seen errors from substitutions complaining that the
result would be longer than (I think) 40000 bytes.
This (I seem to remember) was caused when trying to debug a js error which
involved trying to read a minified version of some js lib (basically remove
newlines, comments etc). I was trying to run:
s/;/;\n/g
To make the file almost readable. I don't have a test case for this I'm afraid.

I know the line is stored internally in the edbrowse buffer faithfully, but I
guess by line length I should have said editable line length (i.e.
the length of line one can perform editing commands on,
regardless of whether the results are fully displayed).

> Like Chuck, my distro doesn't seem to have any js packages beyond 185;
> where can I get 24, and compiling from source is fine,
> in some ways preferable.

What distro?

The download url I used for mozjs 24 is (source version):
https://ftp.mozilla.org/pub/mozilla.org/js/mozjs-24.2.0.tar.bz2

I can't remember what it needs in terms of dependancies, but if you uncompress, cd js/src and the ./configure you should see a whole load of stuff including any failures.

For debugging edbrowse I built with:
./configure --prefix <whereever_you_put_custom_stuff> --disable-optimize --enable-debug
make
make install

The --enable-debug meant I didn't need to mess around with manually setting
CFLAGS etc and the --disable-optimize makes things nicer when using gdb.

As you said, compiling from source in this case really does make life easier.
Even with the debian package's debugging symbols I still needed to use my own
compiled version to get any real debugging done due to the fact that most
(hopefully all) distros will package mozjs 24 with optimizations enabled.

Cheers,
Adam.

  parent reply	other threads:[~2014-01-29 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 21:45 Karl Dahlke
2014-01-28 22:16 ` Chris Brannon
2014-01-29 10:48 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-28 17:35 Karl Dahlke
2014-01-28 21:31 ` Adam Thompson
2014-01-28 11:20 Karl Dahlke
2014-01-28 16:41 ` Chris Brannon
2014-01-28 16:49   ` Adam Thompson
2014-01-28 16:41 ` Adam Thompson
2014-01-28 17:16   ` Chris Brannon
2014-01-28 17:31     ` Cleverson Casarin Uliana
2014-01-29 10:54       ` Adam Thompson

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=20140129104803.GE7404@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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.
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 NNTP newsgroup(s).