unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Felix E. Klee" <felix.klee@inka.de>
Subject: Re: LaTeX-Fill-Paragraph and inline images
Date: Thu, 27 Feb 2003 12:58:44 +0100	[thread overview]
Message-ID: <b3kuhk$m2v$1@sapa.inka.de> (raw)
In-Reply-To: vc97kbmf5jn.fsf@kurasc.kyoto-u.ac.jp

Gernot Hassenpflug wrote:
> Reading through the RefTeX pages on sourceforge, the following link
> from the main page (http://preview-latex.sourceforge.net/) might be
> useful to you and the respondents in the discussion. In particular,
> what is wrong with having say WhizzyTeX open a separate window and
> therefore offers more clarity, while at the same time editing the
> offending text segments with preview-LaTeX quick and dirty. A binding
> of the LaTeX compilation could be done to run both p-L and w-T so that
> updating is synchronized?

Thanks for pointing me to other tools. I have considered them as well but 
there are several arguments that let me favor Preview-LaTeX:
1. I can do all my editing in EMACS, my favorite text editor, and I don't
   have to move my head between a WhizzyTeX window and the editor window.
2. I often work on a Laptop which only has a 1024x768 sized screen and
   having an EMACS and the WhizzyTeX window open at the same time will be
   problematic. In addition the laptop probably isn't fast enough to let
   WhizzyTeX update text in real time (I haven't tried it, though).
3. As for Lyx and Texmacs: I want to have full control over the LaTeX code
   I'm writing and, in addition, I use a lot of macros and 3rd party
   packages.
4. Writing a fill-paragraph function that works properly with Preview-LaTeX
   shouldn't be too hard once we have something similar to compute-motion
   that measures in pixels.

Felix

  reply	other threads:[~2003-02-27 11:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 15:43 LaTeX-Fill-Paragraph and inline images Felix E. Klee
2003-02-09 15:53 ` Kai Großjohann
2003-02-09 16:23   ` Felix E. Klee
2003-02-09 16:37     ` David Kastrup
2003-02-09 17:44       ` Felix E. Klee
2003-02-10 20:38         ` David Kastrup
2003-02-21 15:02           ` Felix E. Klee
2003-02-21 15:50             ` David Kastrup
2003-02-21 23:02               ` Felix E. Klee
2003-02-21 23:18                 ` David Kastrup
2003-02-21 23:35                   ` Glenn Morris
2003-02-21 23:50                 ` Stefan Monnier <foo@acm.com>
2003-02-22  9:44                   ` Felix E. Klee
2003-02-22 20:53                     ` Stefan Monnier
2003-02-22 21:07                       ` Kai Großjohann
2003-02-23 20:20                       ` Felix E. Klee
2003-02-27  9:15                         ` Gernot Hassenpflug
2003-02-27 11:58                           ` Felix E. Klee [this message]
2003-02-27 13:27                             ` David Kastrup
2003-02-21 16:01             ` Stefan Monnier <foo@acm.com>

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='b3kuhk$m2v$1@sapa.inka.de' \
    --to=felix.klee@inka.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).