unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: more LaTeX (was: Re: emacs and beginning of lines)
Date: Wed, 10 Sep 2014 23:55:16 +0200	[thread overview]
Message-ID: <87y4trm98b.fsf@debian.uxu> (raw)
In-Reply-To: mailman.8603.1410341031.1147.help-gnu-emacs@gnu.org

Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:

> No, I mean that with some documents it might be
> non-obvious whether the fragment the point is in is a
> text or programming one.

No, I understood, but that is the only way it could be
possible. How else?

But I think this might be a non-problem in practice. I
did lots of homepages and I never experienced this as a
problem. And I don't remember ever thinking of it
either, so it really cannot be a problem.

Perhaps when you do <html> tags you kind of are
inclined to add new rows to reflect structure, so those
rows never overflow the fill-column. Then when you
start to type the contents of the file, and you get
auto filling as usual.

Or perhaps I just enabled/disabled auto-filling -
usually, setting up the structure is fast. Writing the
contents take more time. It is not unthinkable to do
the <html> without filling, then switch it on and start
to type.

And that would work for LaTeX as well. So perhaps this
isn't a problem after all.

Never heard of LuaTeX but it doesn't supprise me because
Lua seems to be like a "glue" language (perhaps as Perl
used to be) that just appears and sticks between the
bigger and bulkier building blocks...

-- 
underground experts united


  parent reply	other threads:[~2014-09-10 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06  9:59 emacs and beginning of lines Jude DaShiell
2014-09-06 11:03 ` Teemu Likonen
2014-09-07  0:17   ` Jude DaShiell
     [not found]   ` <mailman.8378.1410049068.1147.help-gnu-emacs@gnu.org>
2014-09-07 18:35     ` Emanuel Berg
2014-09-07 20:47   ` Marcin Borkowski
     [not found]   ` <mailman.8416.1410122851.1147.help-gnu-emacs@gnu.org>
2014-09-07 21:32     ` Emanuel Berg
2014-09-08  9:17       ` Marcin Borkowski
2014-09-08 11:31         ` Yuri Khan
2014-09-08 11:34         ` Yuri Khan
2014-09-08 12:21           ` Marcin Borkowski
2014-09-08 12:34             ` Stefan Monnier
     [not found]             ` <mailman.8453.1410179680.1147.help-gnu-emacs@gnu.org>
2014-09-08 22:14               ` Emanuel Berg
     [not found]       ` <mailman.8445.1410167872.1147.help-gnu-emacs@gnu.org>
2014-09-08 22:10         ` Emanuel Berg
2014-09-09  7:58           ` Marcin Borkowski
     [not found]           ` <mailman.8505.1410249559.1147.help-gnu-emacs@gnu.org>
2014-09-09 20:02             ` more LaTeX (was: Re: emacs and beginning of lines) Emanuel Berg
2014-09-10  0:12               ` Marcin Borkowski
     [not found]               ` <mailman.8575.1410307953.1147.help-gnu-emacs@gnu.org>
2014-09-10  1:12                 ` Emanuel Berg
2014-09-10  9:23                   ` Marcin Borkowski
     [not found]                   ` <mailman.8603.1410341031.1147.help-gnu-emacs@gnu.org>
2014-09-10 21:55                     ` Emanuel Berg [this message]
2014-09-10 23:42                       ` Marcin Borkowski

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=87y4trm98b.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@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.
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).