From: Bastien Guerry <bzg@altern.org>
To: Vivien Mallet <Vivien.Mallet@inria.fr>
Cc: 681-done@debbugs.gnu.org
Subject: bug#681: Wrong C++ indentation in batch mode
Date: Tue, 07 Jan 2014 11:26:13 +0100 [thread overview]
Message-ID: <87zjn8hu79.fsf@bzg.ath.cx> (raw)
In-Reply-To: <200808091726.22907.Vivien.Mallet@inria.fr> (Vivien Mallet's message of "Sat, 9 Aug 2008 17:26:22 +0200")
Hi Vivien,
Vivien Mallet <Vivien.Mallet@inria.fr> writes:
> The indentation in C++ mode does not seem to work properly in batch mode with
> the following code (indented in interactive mode):
> """
> template <class A, class B>
> Derived<A, B>::Derived():
> Base<A,
> B>() // Problem: wrong indentation in batch mode.
> {
> }
> """
>
> Now, define the Lisp function:
> (defun cpp_indent ()
> (c-set-style "gnu")
> (c++-mode)
> (indent-region (point-min) (point-max) ())
> (save-buffer)
> )
> And apply it the previous function. It will result in:
> """
> template <class A, class B>
> Derived<A, B>::Derived():
> Base<A,
> B>() // Problem: wrong indentation in batch mode.
> {
> }
> """
> which is inconsistent with the interactive and is not, I presume, the
> targeted result.
I can't reproduce this. I get the correct indentation.
I'm closing this bug report, feel free to reopen it if needed.
--
Bastien
next prev parent reply other threads:[~2014-01-07 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 15:26 bug#681: Wrong C++ indentation in batch mode Vivien Mallet
2008-08-10 16:42 ` OFFICE ZERO
[not found] ` <handler.681.B681.12183870793367.ackinfo@emacsbugs.donarmstrong.com>
2008-08-10 17:10 ` bug#681: Info received (bug#681: Wrong C++ indentation in batch mode) OFFICE ZERO
[not found] ` <handler.681.B681.121838828710091.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11 1:17 ` bug#681: Info received (bug#681: Info received (bug#681: Wrong C++ indentation in batch mode)) OFFICE ZERO
2008-08-10 17:01 ` bug#681: Wrong C++ indentation in batch mode OFFICE ZERO
[not found] ` <handler.681.B681.12183876726365.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11 1:17 ` bug#681: Info received (bug#681: Wrong C++ indentation in batch mode) OFFICE ZERO
2008-08-10 17:11 ` bug#681: Wrong C++ indentation in batch mode OFFICE ZERO
[not found] ` <handler.681.B681.121838833410165.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11 1:16 ` bug#681: Info received (bug#681: Wrong C++ indentation in batch mode) OFFICE ZERO
2008-08-10 17:12 ` bug#681: Wrong C++ indentation in batch mode OFFICE ZERO
[not found] ` <handler.681.B681.121838833410168.ackinfo@emacsbugs.donarmstrong.com>
2008-08-11 1:07 ` bug#681: Info received (bug#681: Wrong C++ indentation in batch mode) OFFICE ZERO
2014-01-07 10:26 ` Bastien Guerry [this message]
2014-01-07 15:36 ` bug#681: Wrong C++ indentation in batch mode Vivien Mallet
2014-01-07 16:09 ` Bastien
2015-12-29 1:18 ` Andrew Hyatt
2015-12-29 22:02 ` Alan Mackenzie
2016-01-04 23:16 ` Alan Mackenzie
2016-01-26 4:46 ` Andrew Hyatt
2016-02-06 12:05 ` Vivien Mallet
2016-02-07 22:09 ` Alan Mackenzie
2016-02-07 22:10 ` Vivien Mallet
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=87zjn8hu79.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=681-done@debbugs.gnu.org \
--cc=Vivien.Mallet@inria.fr \
/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).