From: MON KEY <monkey@sandpframing.com>
To: tzz@lifelogs.com
Cc: emacs-devel@gnu.org
Subject: view/edit large files (was: map-file-lines)
Date: Fri, 6 Feb 2009 22:44:30 -0500 [thread overview]
Message-ID: <d2afcfda0902061944k312e67d4hc285ff841d803de4@mail.gmail.com> (raw)
> [1] I still can't think of a better term than "window."
> large-file-window is too verbose. boffset? byte-offset?
> virtual-buffer?
off-slice
slice-off
virtual-slice
s_P
next reply other threads:[~2009-02-07 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 3:44 MON KEY [this message]
2009-02-08 4:34 ` view/edit large files (was: map-file-lines) Bob Rogers
2009-02-09 19:44 ` view/edit large files Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2009-02-04 15:38 map-file-lines Ted Zlatanov
2009-02-05 5:40 ` map-file-lines Richard M Stallman
2009-02-06 18:42 ` view/edit large files (was: map-file-lines) Ted Zlatanov
2009-02-07 9:14 ` Richard M Stallman
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=d2afcfda0902061944k312e67d4hc285ff841d803de4@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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 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).