unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sergio Pokrovskij <sergio@none.nowhere.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Getting Emacs to play nice with Hunspell and apostrophes
Date: Sun, 15 Jun 2014 09:48:05 +0700	[thread overview]
Message-ID: <87d2eavqfu.fsf@none.nowhere.invalid> (raw)
In-Reply-To: mailman.3627.1402724759.1147.help-gnu-emacs@gnu.org

I can't tell you how much I dislike the ugly quotes in Emacs Info,
e.g.

╭────
│ `C-c C-a     (`org-attach')'
│    The dispatcher for commands related to the attachment system.
╰────

I always use paired quotes, but normally I use the ASCII
apostrophe.  I admit this causes problems for the speller with
e.g. the Wikipedia convention about its representation of
''italics'', '''bold face''' etc.

>>>>> "Yuri" == Yuri Khan skribis:

[...]

  Yuri> Now let me tell you how I do curly quotes.

  Yuri> First, with my right thumb, I hold the AltGr
  Yuri> modifier. Then, I press k and l in sequence to get a
  Yuri> balanced pair of double curly quotes, or ; and ' for
  Yuri> single quotes (I customized my xkb configuration files to
  Yuri> get this but it works similarly with the out-of-the-box
  Yuri> config).

In Emacs I use (on both Linux and MS Windows):

C-c 6  to produce the English 66-99 pair “_”
C-c 9  to produce the German 99-66 pair „_“
C-c "  to produce the French angular pair «_»

The point gets positioned in between:

--8<---------------cut here---------------start------------->8---
(defun insert-66-99 ()
  "Make a pair of 66-99 quotes and be positioned to type inside."
  (interactive)
  (insert "“”")
  (backward-char))

(global-set-key "\C-c6" 'insert-66-99)
--8<---------------cut here---------------end--------------->8---

-- 
Sergio


  parent reply	other threads:[~2014-06-15  2:48 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3187.1402155569.1147.help-gnu-emacs@gnu.org>
2014-06-11  0:04 ` Getting Emacs to play nice with Hunspell and apostrophes Emanuel Berg
2014-06-11  5:23   ` Nikolai Weibull
     [not found]   ` <mailman.3375.1402464243.1147.help-gnu-emacs@gnu.org>
2014-06-11 14:24     ` Emanuel Berg
2014-06-11 15:03       ` Nikolai Weibull
     [not found]       ` <mailman.3418.1402499010.1147.help-gnu-emacs@gnu.org>
2014-06-11 15:20         ` Emanuel Berg
2014-06-11 16:57           ` Teemu Likonen
     [not found]           ` <mailman.3437.1402505846.1147.help-gnu-emacs@gnu.org>
2014-06-11 21:32             ` Emanuel Berg
2014-06-12  5:43           ` Yuri Khan
2014-06-12 12:51             ` Stefan Monnier
2014-06-12 13:36               ` Nikolai Weibull
2014-06-12 14:48                 ` Stefan Monnier
     [not found]               ` <mailman.3496.1402580195.1147.help-gnu-emacs@gnu.org>
2014-06-14  1:49                 ` Emanuel Berg
2014-06-14  5:45                   ` Yuri Khan
2014-06-17  1:09                     ` Keyboard layout purpose (was: Getting Emacs to play nice with Hunspell and apostrophes) Garreau, Alexandre
     [not found]                   ` <mailman.3627.1402724759.1147.help-gnu-emacs@gnu.org>
2014-06-14 11:14                     ` Getting Emacs to play nice with Hunspell and apostrophes Emanuel Berg
2014-06-14 14:51                       ` Yuri Khan
2014-06-14 15:26                         ` Teemu Likonen
2014-06-17  1:42                         ` Garreau, Alexandre
     [not found]                       ` <mailman.3651.1402757512.1147.help-gnu-emacs@gnu.org>
2014-06-14 16:13                         ` Emanuel Berg
2014-06-16 15:35                           ` Joost Kremers
2014-06-17  2:21                           ` Garreau, Alexandre
     [not found]                           ` <mailman.3799.1402971688.1147.help-gnu-emacs@gnu.org>
2014-06-17  2:41                             ` Rusi
2014-06-17  3:05                               ` Rusi
2014-06-17  1:46                       ` Garreau, Alexandre
2014-06-15  2:48                     ` Sergio Pokrovskij [this message]
2014-06-17  1:30                       ` Garreau, Alexandre
2014-06-12 16:58             ` Eli Zaretskii
     [not found]           ` <mailman.3473.1402551809.1147.help-gnu-emacs@gnu.org>
2014-06-14  1:35             ` Emanuel Berg
2014-06-14  2:38             ` Emanuel Berg
2014-06-14  5:19               ` Facts for fans: encodings history (was: Re: Getting Emacs to play nice with Hunspell and apostrophes) Emanuel Berg
2014-06-14  7:37                 ` Yuri Khan
2014-06-14  8:28                   ` Eli Zaretskii
2014-06-14 10:46                     ` Yuri Khan
     [not found]                 ` <mailman.3631.1402731427.1147.help-gnu-emacs@gnu.org>
2014-06-14 11:21                   ` Emanuel Berg
2014-06-14  7:11               ` Getting Emacs to play nice with Hunspell and apostrophes Yuri Khan
     [not found]               ` <mailman.3630.1402729917.1147.help-gnu-emacs@gnu.org>
2014-06-14 11:20                 ` Emanuel Berg
2014-06-17  2:12 ` Rusi
2014-06-17  2:33   ` Garreau, Alexandre
2014-06-07 15:39 Nikolai Weibull
2014-06-07 17:43 ` Robert Thorpe
2014-06-07 17:59   ` Yuri Khan
2014-06-07 18:18   ` Nikolai Weibull
2014-06-07 17:53 ` Sharon Kimble
2014-06-07 18:17   ` Eli Zaretskii
2014-06-07 18:28 ` Nikolai Weibull
2014-06-07 18:40   ` Eli Zaretskii
2014-06-07 19:59     ` Nikolai Weibull

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=87d2eavqfu.fsf@none.nowhere.invalid \
    --to=sergio@none.nowhere.invalid \
    --cc=help-gnu-emacs@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.
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).