unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "George O'Hara" <georgeohara92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 41284@debbugs.gnu.org
Subject: bug#41284: 26.3; cc-mode: Incorrect font locking of static functions
Date: Fri, 15 May 2020 13:03:39 +0100	[thread overview]
Message-ID: <CAHHF0DZMG9c0Pt3LSfx5VOg5sQW4=JAV1YYuKEYWDA9hQ3U7DA@mail.gmail.com> (raw)
In-Reply-To: <83v9kx1kds.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

Hi Eli!

Yes, I do mean the other way round.
I made a post on the Emacs SE with images last night, which may be useful
to link here.
https://emacs.stackexchange.com/questions/58509/static-function-highlighting-locking-in-c?noredirect=1#comment91178_58509

As an aside, I accidentally posted this bug twice. Is there a way I can
close the other issue?

Kind regards

On Fri, 15 May 2020 at 12:57, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: "George O'Hara" <georgeohara92@gmail.com>
> > Date: Fri, 15 May 2020 12:15:42 +0100
> >
> > >From 'emacs -Q', C-x C-f and create a buffer called 'test.c'.
> > In this buffer, type:
> >
> > static int some_function();
> > int static another_function();
> >
> > some_function is not highlighted, while another_function is.
>
> You mean, the other way around, no?
>

[-- Attachment #2: Type: text/html, Size: 1494 bytes --]

  reply	other threads:[~2020-05-15 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 11:15 bug#41284: 26.3; cc-mode: Incorrect font locking of static functions George O'Hara
2020-05-15 11:57 ` Eli Zaretskii
2020-05-15 12:03   ` George O'Hara [this message]
2020-05-17 19:26     ` Alan Mackenzie
     [not found]       ` <CAHHF0DZ_wUH92NS+Nf0-qQL1zzSQTBPd7xEY1MDXQunt0mf9hA@mail.gmail.com>
2020-05-18 18:38         ` Alan Mackenzie

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='CAHHF0DZMG9c0Pt3LSfx5VOg5sQW4=JAV1YYuKEYWDA9hQ3U7DA@mail.gmail.com' \
    --to=georgeohara92@gmail.com \
    --cc=41284@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).