From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Roman E <re@just.ask.me.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Weird Tabbing Effects
Date: Wed, 2 Apr 2008 11:06:06 +0200 [thread overview]
Message-ID: <B001C9A4-97DB-4AC9-9B53-B9B17DE65FD9@Web.DE> (raw)
In-Reply-To: <fsu38r$sgq$1@tabloid.srv.ualberta.ca>
Am 01.04.2008 um 21:43 schrieb Roman E:
> Is there any way I can fix these files so that they're viewable in
> other editors? Also, what caused this problem?
Just make sure that all programmes use the same tab width! This value
can be set on mechanical typewriter machines as well as in
applications. Well, there is also a side-effect with fonts:
proportional fonts can make problems.
--
Greetings
Pete
Isn't vi that text editor with two modes... one that beeps and one
that corrupts your file?
– Dan Jacobson, on comp.os.linux.advocacy
next prev parent reply other threads:[~2008-04-02 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 19:43 Weird Tabbing Effects Roman E
2008-04-02 9:06 ` Peter Dyballa [this message]
2008-04-02 9:49 ` Tassilo Horn
2008-04-02 9:13 ` Anders Wirzenius
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=B001C9A4-97DB-4AC9-9B53-B9B17DE65FD9@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=re@just.ask.me.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.
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).