From: Marcelo Toledo <marcelo@marcelotoledo.org>
Cc: Turadg Aleahmad <turadg@users.sourceforge.net>
Subject: Re: indentation issues when editing a PHP file
Date: Fri, 26 Mar 2004 16:03:59 -0400 [thread overview]
Message-ID: <87n063nzo0.fsf@kali.intranet> (raw)
In-Reply-To: <20040326173451.6525.qmail@web13004.mail.yahoo.com> (Saifi Khan's message of "Fri, 26 Mar 2004 09:34:51 -0800 (PST)")
it is wrong, it forces you to write it as:
class test
{
function test() {
}
}
but, as you are saying, i code like:
class test {
function test()
{
code();
}
}
i am copying to the maintainer of php-mode so he can take a look at
this.
Saifi Khan <saifixkhan@yahoo.com> writes:
> Hi:
>
>
> When editing a PHP file, the '{' curly brace
> positions itself as indicated below.
>
>
> class Log
> {
> function log( $msg )
> ...{
> ...}
> }
>
> the dots (.) are for indicating the spaces.
>
>
> The following indentation style is what I would like to see.
>
>
> class Log
> {
> function log( $msg )
> {
> }
> }
>
>
> I have spent sometime looking at the .emacs file, indentation options
> and other mails on the mailing list.
>
>
> I have been able to setup CCmode for C, C++ and Java,
> however this just beats me.
>
> What options should I place in my php-hook-function ?
> I will appreciate suggestions to solve this problem.
>
>
> thanks
> Saifi.
>
> Ps. please see the attached .emacs file
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance Tax Center - File online. File on time.
> http://taxes.yahoo.com/filing.html
>
> _______________________________________________
> Help-gnu-emacs mailing list
> Help-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
--
Marcelo Toledo
marcelo@marcelotoledo.org
http://www.marcelotoledo.org
Mobile: 55 71 9141-7181
next prev parent reply other threads:[~2004-03-26 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 17:34 indentation issues when editing a PHP file Saifi Khan
2004-03-26 20:03 ` Marcelo Toledo [this message]
2004-03-27 6:29 ` Emory Smith
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=87n063nzo0.fsf@kali.intranet \
--to=marcelo@marcelotoledo.org \
--cc=turadg@users.sourceforge.net \
/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).