From: Eli Zaretskii <eliz@gnu.org>
To: Anoj Perera <anojmperera@gmail.com>
Cc: 7659@debbugs.gnu.org
Subject: bug#7659: emacs - c mode tab space different between windows and linux
Date: Fri, 17 Dec 2010 13:00:46 +0200 [thread overview]
Message-ID: <83aak4hdep.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTikr0vqNvcZzaURLe+RezWQZ5+2OMJT8Eu+KMmuo@mail.gmail.com>
> From: Anoj Perera <anojmperera@gmail.com>
> Date: Fri, 17 Dec 2010 09:59:37 +0000
>
> Hi many thanks for your reply. Haven't tried the -Q option (without
> loading the .emacs file?).
Please do. I think you will discover that the display on Ubuntu will
then look exactly like that on Windows.
And please keep 7659@debbugs.gnu.org on the list of addressees, so
this whole discussion gets recorded in the history of your bug report.
> I've attached a source file coded with
> emacs in linux (Ubuntu 10.04) and a screenshot same file viewed in
> emacs in Windows. You can note the diference, function name and
> arguments are indented little too much.
I see your file exactly like in the screenshot, both on Windows and on
GNU/Linux. So I think you have some site init file on Ubuntu that
sets certain options related to C indentation. "emacs -Q" will bypass
the customizations on that file, so you will know this for sure.
If this is indeed the case, you should look at your site init file,
and do the same on Windows.
> I am guessing this is a character encoding issue.
No, character encoding doesn't (and cannot) have anything with
indentation. It's just that (if my guess is right) on Ubuntu you have
some customizations that you need to have on your Windows .emacs, and
then you will see the same display.
next prev parent reply other threads:[~2010-12-17 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 22:50 bug#7659: emacs - c mode tab space different between windows and linux Anoj Perera
2010-12-17 8:15 ` Eli Zaretskii
[not found] ` <AANLkTikr0vqNvcZzaURLe+RezWQZ5+2OMJT8Eu+KMmuo@mail.gmail.com>
2010-12-17 11:00 ` Eli Zaretskii [this message]
2010-12-17 11:30 ` Anoj Perera
2010-12-17 17:45 ` Anoj Perera
2010-12-17 18:23 ` Jan Djärv
2010-12-17 21:51 ` Anoj Perera
2010-12-17 22:53 ` Eli Zaretskii
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=83aak4hdep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7659@debbugs.gnu.org \
--cc=anojmperera@gmail.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).