After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 616294 - Keyboard character fault
Keyboard character fault
Status: RESOLVED DUPLICATE of bug 634488
Product: gedit
Classification: Applications
Component: general
2.30.x
Other Mac OS
: Normal major
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-20 15:24 UTC by Alan
Modified: 2012-01-08 19:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alan 2010-04-20 15:24:31 UTC
ALSO IN GEdit 2.28.3

First can I say thank you for doing a MAC port, great effort.  However,
there is a REALLY SERIOUS error in that the 'hash' symbol - alt-3 on UK
(British) keyboards does not work. I use gedit every day on my Linux
machine and was delighted to discover a MAC port had been developed -
great, I can do all my editing with the same great tool on all my
computers :)  However, I was surprised to discover when trying the MAC port for
the first time to write some C/C++ code, only to find the #
symbol is not available!! making (OS X) gedit useless for programming.

I did discover that it is possible to add a # symbol using the built-in
TextEdit app, then copy and paste hash symbol into Gedit, but that is
really not a reasonable solution.

I realise that the majority of users are on Linux and that Mac users are
probably in the minority, but if this can be fixed soon I would be
grateful.  I would like to use the same great editor on all my machines.

Thanks in anticipation.
Alan Lewis
Comment 1 Daniel Arteaga 2010-05-29 18:46:30 UTC
Same problem here.
Comment 2 jessevdk@gmail.com 2012-01-08 19:00:44 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 634488 ***