unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: .emacs poser
Date: Wed, 18 Dec 2013 00:25:42 +0100	[thread overview]
Message-ID: <87ppovoy9c.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: 871u1bqeqe.fsf@nl106-137-194.student.uu.se

Emanuel Berg <embe8573@student.uu.se> writes:

> I should be possible to set the default somehow, or,
> if not so, this should be solvable with hooks, the
> Emacs poor-man's solution for everything when
> everything else fails.

I got it working like this. It will be interesting to
see if it works out.

(quail-define-package "swedish-quail" "Swedish" "Swedish quail")

(quail-define-rules
 ("0A" ?Å) ("0a" ?å)
 (":A" ?Ä) (":a" ?ä)
 (":O" ?Ö) (":o" ?ö) )
(set-input-method 'swedish-quail) ;; add this to text-mode-hook etc.

In the docstring to the `quail-define-package', there
is an optional argument described like this:

;; GUIDANCE specifies how a guidance string is shown in
;; echo area.  If it is t, list of all possible
;; translations for the current key is shown with the
;; currently selected translation being highlighted.
;; If it is an alist, the element has the form (CHAR
;; . STRING).  Each character in the current key is
;; searched in the list and the corresponding string is
;; shown.  If it is nil, the current key is shown.

However, is it not possible to entirely disable the
echo area fanfare? I think it is just disruptive.

-- 
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united:  http://user.it.uu.se/~embe8573


  reply	other threads:[~2013-12-17 23:25 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  0:01 .emacs poser B. T. Raven
2013-12-17  0:36 ` Emanuel Berg
2013-12-17  1:48 ` Dale Snell
2013-12-17  2:46   ` Drew Adams
     [not found] ` <mailman.9443.1387244913.10748.help-gnu-emacs@gnu.org>
2013-12-17  2:03   ` Emanuel Berg
2013-12-17  2:58     ` Dale Snell
2013-12-17  5:53       ` Jambunathan K
     [not found]     ` <mailman.9453.1387249112.10748.help-gnu-emacs@gnu.org>
2013-12-17  3:16       ` Emanuel Berg
2013-12-17  5:32         ` Dale Snell
2013-12-17  6:27         ` Tilman Ahr
2013-12-17 16:42           ` Emanuel Berg
2013-12-18  2:25             ` Tilman Ahr
2013-12-18 21:17               ` Emanuel Berg
2013-12-18  3:01             ` Yuri Khan
     [not found]             ` <mailman.9542.1387335681.10748.help-gnu-emacs@gnu.org>
2013-12-18 21:23               ` Emanuel Berg
2013-12-19  1:13                 ` Yuri Khan
     [not found]                 ` <mailman.9626.1387415627.10748.help-gnu-emacs@gnu.org>
2013-12-20  1:40                   ` Emanuel Berg
     [not found]         ` <mailman.9460.1387258387.10748.help-gnu-emacs@gnu.org>
2013-12-17 16:17           ` Emanuel Berg
2013-12-17 17:36             ` Dale Snell
     [not found]             ` <mailman.9507.1387301817.10748.help-gnu-emacs@gnu.org>
2013-12-17 17:41               ` Emanuel Berg
2013-12-17  3:06 ` Yuri Khan
2013-12-17 15:17   ` Drew Adams
2013-12-18  1:38     ` Yuri Khan
2013-12-17  7:41 ` Kevin Rodgers
2013-12-17 15:24 ` Doug Lewan
     [not found] ` <mailman.9465.1387266001.10748.help-gnu-emacs@gnu.org>
2013-12-17 15:40   ` Sebastien Vauban
2013-12-17 16:29     ` Drew Adams
2013-12-17 16:49     ` Emanuel Berg
2013-12-17 18:20     ` Eli Zaretskii
     [not found] ` <mailman.9492.1387293902.10748.help-gnu-emacs@gnu.org>
2013-12-17 17:14   ` Emanuel Berg
2013-12-17 17:16   ` Emanuel Berg
2013-12-17 19:04     ` Doug Lewan
     [not found]     ` <mailman.9512.1387307070.10748.help-gnu-emacs@gnu.org>
2013-12-17 22:42       ` Emanuel Berg
2013-12-17 23:35         ` Doug Lewan
2013-12-17 21:15   ` Joost Kremers
2013-12-17 22:44     ` Emanuel Berg
2013-12-17 23:25       ` Emanuel Berg [this message]
2013-12-18  3:22     ` Jambunathan K
     [not found]     ` <mailman.9544.1387337046.10748.help-gnu-emacs@gnu.org>
2013-12-18 21:42       ` Emanuel Berg
     [not found]         ` <mailman.9628.1387418319.10748.help-gnu-emacs@gnu.org>
2013-12-19  2:52           ` Emanuel Berg
2013-12-19  3:00             ` Emanuel Berg
2013-12-20  5:31             ` Jambunathan K
2013-12-20  5:38               ` Jambunathan K
     [not found]             ` <mailman.9724.1387517532.10748.help-gnu-emacs@gnu.org>
2013-12-20 17:52               ` Emanuel Berg
2013-12-27  6:00                 ` B. T. Raven
2013-12-27 14:12                   ` Yuri Khan
2013-12-27 16:11                     ` Drew Adams
     [not found]                     ` <mailman.10526.1388160732.10748.help-gnu-emacs@gnu.org>
2013-12-29 22:17                       ` B. T. Raven
2013-12-29 23:48                         ` Drew Adams
2013-12-20  1:52         ` Jambunathan K
2013-12-19 22:24       ` Joost Kremers
2013-12-19 23:16         ` Emanuel Berg

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=87ppovoy9c.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --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).