ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <WhiteG@mar.dfo-mpo.gc.ca>
Cc: "George N. White III" <WhiteG@mar.dfo-mpo.gc.ca>,
	ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: texfont bad mode (755->0755) for mkdir, missing map line
Date: Thu, 15 Nov 2001 12:06:38 -0400 (AST)	[thread overview]
Message-ID: <Pine.GSO.4.40.0111151200460.2255-100000@emerald.bio.dfo.ca> (raw)
In-Reply-To: <5.1.0.14.1.20011115093340.03230490@server-1>

On Thu, 15 Nov 2001, Hans Hagen wrote:

> At 04:24 PM 11/14/2001 -0400, George N. White III wrote
>
> >The misplaced "0" appears in the line which strips any existing entries
> >for the current font ($thename) from $mapdata:
> >
> >        { $mapdata =~ s/^$thename\s.*?$//gmois ;
>
> ah, that's a stupid error, thanks for locating it. About the 'o' key, does
> it also optimized the replacement text, i.e., should i also change:
>
>   s/(--en.*\=)\?/$1$encoding/io ;

I wouldn't call it a stupid error -- it is all too easy to type that
'o' when writing perl code if you have a bunch of expressions where
the pattern doesn't change.

I think the 'o' flag only applies to the search pattern, but to be
sure I'd have to use the sources.

-- 
George N. White III <gnw3@acm.org> Bedford Institute of Oceanography


  reply	other threads:[~2001-11-15 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.40.0111122014370.12541-100000@emerald.bio.dfo.c a>
2001-11-13  8:26 ` Hans Hagen
2001-11-13 16:11   ` George N. White III
2001-11-13 17:46   ` Olaf Weber
2001-11-14 20:24   ` George N. White III
     [not found]   ` <Pine.GSO.4.40.0111141607490.23556-100000@emerald.bio.dfo.c a>
2001-11-15  8:35     ` Hans Hagen
2001-11-15 16:06       ` George N. White III [this message]
2001-11-13  0:28 George N. White III

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=Pine.GSO.4.40.0111151200460.2255-100000@emerald.bio.dfo.ca \
    --to=whiteg@mar.dfo-mpo.gc.ca \
    --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).