ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Surprising changes in vers. 2012.01.11
Date: Wed, 11 Jan 2012 17:33:11 +0100	[thread overview]
Message-ID: <20120111163311.GB99455@iram-ha-003840.extra.cea.fr> (raw)
In-Reply-To: <20120111162449.GA99455@iram-ha-003840.extra.cea.fr>

On Wed, Jan 11, 2012 at 05:24:51PM +0100, Alan Braslau wrote:
> On Wed, Jan 11, 2012 at 04:23:28PM +0100, Hans Hagen wrote:
> > 
> > indeed, and it's a bonus that ~ == nobreakspace (although I can imagine 
> > that we'd get rid of it) but defining other macros in terms of active 
> > characters is a bad idea
> > 
> > (in fact one can use the unicode nbsp character)
> > 
> 
> I have always liked this TeX active character (~).
> 
> As information for users of X11:
> setxkbmap -option nbsp:level2
> (and the equivalent in "xorg.conf" or "etc/hal/fdi/policy/x11-init.fdi")
> gives nbsp as shift+space.
> 
> On the subject of unicode characters,
> I just discovered the ":dig" command (diagraphs)
> under my favorite editor "vim"!

Follow-up:

:se list lcs=nbsp:~

makes me feel right at home with my traditional TeX usage...

Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-01-11 16:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 12:22 Steffen Wolfrum
2012-01-11 12:40 ` Steffen Wolfrum
2012-01-11 12:50   ` Steffen Wolfrum
2012-01-11 13:01     ` Hans Hagen
2012-01-11 13:17       ` Thomas A. Schmitz
2012-01-11 13:41         ` Hans Hagen
2012-01-11 14:38     ` Steffen Wolfrum
2012-01-11 14:45       ` luigi scarso
2012-01-11 14:46         ` luigi scarso
2012-01-11 15:18           ` Steffen Wolfrum
2012-01-11 15:26             ` Hans Hagen
2012-01-11 15:36             ` luigi scarso
2012-01-11 15:55               ` Wolfgang Schuster
2012-01-11 15:23           ` Hans Hagen
2012-01-11 16:24             ` Alan Braslau
2012-01-11 16:33               ` Alan Braslau [this message]
2012-01-11 16:42                 ` Hans Hagen
2012-01-11 17:32                   ` Khaled Hosny
2012-01-11 15:48       ` Steffen Wolfrum
2012-01-11 15:53         ` Hans Hagen
2012-01-11 16:46         ` Steffen Wolfrum
2012-01-11 19:31           ` Wolfgang Schuster
2012-01-11 19:44             ` Steffen Wolfrum
2012-01-11 19:51               ` Wolfgang Schuster
2012-01-11 21:05                 ` Hans Hagen
2012-01-11 21:04             ` Hans Hagen
2012-01-12 21:20           ` Steffen Wolfrum
2012-01-11 12:53 ` Hans Hagen
2012-01-11 12:55 ` luigi scarso
2012-01-11 13:43   ` Hans Hagen
2012-01-12  8:58 ` Mari Voipio
2012-01-12  9:10   ` luigi scarso

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120111163311.GB99455@iram-ha-003840.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).