unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: John Chapple <jrchapple@sympatico.ca>
Cc: Reto Zimmermann <reto@gnu.org>,
	"22368@debbugs.gnu.org" <22368@debbugs.gnu.org>
Subject: bug#22368: Another way to produce the same result
Date: Fri, 14 Aug 2020 22:34:40 -0700	[thread overview]
Message-ID: <CADwFkmmymAm0C5esVgm0NhQw3RegPkRTQpkq5k1YpJ-w110a+g@mail.gmail.com> (raw)
In-Reply-To: <BAY173-W40AEF2296C05153E8F9E1FCACC0@phx.gbl> (John Chapple's message of "Thu, 14 Jan 2016 17:10:44 +0000")

Hi Reto,

Could you please help take a look at the below bug report in vhdl-mode?
It was reported over 4 years ago but unfortunately never got a reply at
the time.

Thanks in advance.

Best regards,
Stefan Kangas

John Chapple <jrchapple@sympatico.ca> writes:

> Hello again, Ladies and/or Gentlemen,
>
> I have found another method to reproduce this problem that perhaps is clearer:
>
> Open the attached file.
>
> Using the mouse, select Edit | Select All .
>
> Using the mouse, select VHDL | Comment | (Un)Comment Out Region.
>
> Line 14 will now be rejected by any VHDL compiler.  The file is saved to disk as it appears on the screen.  I checked with another editor.
>
> Cheers
> John





  reply	other threads:[~2020-08-15  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  0:12 bug#22368: vhdl comment-uncomment problem, apparently (or not) related to 14335 and 5997 John Chapple
2016-01-14 17:10 ` bug#22368: Another way to produce the same result John Chapple
2020-08-15  5:34   ` Stefan Kangas [this message]
2020-08-18 10:43     ` Reto Zimmermann
2020-08-18 11:39       ` Stefan Kangas
2020-08-19 11:52         ` Reto Zimmermann
2021-12-02  8:48           ` bug#22368: vhdl comment-uncomment problem, apparently (or not) related to 14335 and 5997 Lars Ingebrigtsen

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=CADwFkmmymAm0C5esVgm0NhQw3RegPkRTQpkq5k1YpJ-w110a+g@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=22368@debbugs.gnu.org \
    --cc=jrchapple@sympatico.ca \
    --cc=reto@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).