unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Theodor Thornhill <theo@thornhill.no>
To: Ergus <spacibba@aol.com>
Cc: Eli Zaretskii <eliz@gnu.org>, casouri@gmail.com, emacs-devel@gnu.org
Subject: Re: Missing features in c-ts-mode
Date: Fri, 17 Feb 2023 19:43:57 +0100	[thread overview]
Message-ID: <87k00g16aa.fsf@thornhill.no> (raw)
In-Reply-To: <20230217182707.bsiwlesafcvkk46u@Ergus>

Ergus <spacibba@aol.com> writes:

> On Fri, Feb 17, 2023 at 07:10:28PM +0100, Theodor Thornhill wrote:
>>
>>
>>On 17 February 2023 19:02:28 CET, Ergus <spacibba@aol.com> wrote:
>>
>>Yep! Is there any particular style? Would pragmas be indented from the parent scope, and the next line after it be at the same level as the pragma?
>>
>>Theo
>>
>
> Hi:
>
> Yes, pragmas will be generally indented from the parent scope,
> continuation lines are usually in the same level or one level more,
>
> And then everything continues as usual:
>
> These are the common use cases I know so far:
>
> // outline pragmas
> #pragma bla
> int myfunction1()
> {...}
>
> int main()
> {
>      // inline pragmas for functions
>      #pragma bla bla
>      somefunction1()
>
>      // inline pragmas for function with continuation one level more
>      #pragma bla bla\
>          the continuation of pragma
>      somefunction2()
>
>      // inline pragma for a block of code
>      #pragma bla2
>      {
>          this is a block as usual
>
>          // nested pragma
>          #pragma mynestedpragma
>          bla()
>      }
> }
>
> Best and thanks,
> Ergus

Great, thanks!  I think I have a good idea about what you want, and I'll
see if I can come up with something.

Theo



  reply	other threads:[~2023-02-17 18:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 17:59 Missing features in c-ts-mode Eli Zaretskii
2023-02-15 18:29 ` Theodor Thornhill
2023-02-15 19:05   ` Eli Zaretskii
2023-02-15 19:18     ` Theodor Thornhill
2023-02-15 19:31       ` Theodor Thornhill
2023-02-15 19:48         ` Eli Zaretskii
2023-02-15 19:59           ` Theodor Thornhill
2023-02-16 19:14             ` Theodor Thornhill
2023-02-16 20:38               ` Eli Zaretskii
2023-02-16 21:05                 ` Theodor Thornhill
2023-02-17  8:29               ` Ergus
2023-02-17  8:42                 ` Eli Zaretskii
2023-02-17  9:56                 ` Theodor Thornhill
2023-02-17 12:20                   ` Eli Zaretskii
2023-02-17 16:37                     ` Ergus
2023-02-17 17:34                       ` Theodor Thornhill
2023-02-17 18:02                         ` Ergus
2023-02-17 18:10                           ` Theodor Thornhill
2023-02-17 18:27                             ` Ergus
2023-02-17 18:43                               ` Theodor Thornhill [this message]
2023-02-15 20:31           ` Felix
2023-02-16  7:35             ` Eli Zaretskii
2023-02-16  8:08               ` Theodor Thornhill
2023-02-16 12:10               ` Felix
2023-02-15 20:03       ` Eli Zaretskii
2023-02-15 20:21         ` Theodor Thornhill
2023-02-16  7:04           ` 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=87k00g16aa.fsf@thornhill.no \
    --to=theo@thornhill.no \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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).