Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread Russ Allbery
Steve McIntyre writes: > The Wanderer wrote: >> At a guess, probably "herb", which is commonly pronounced without the >> initial aspirant even in dialects (etc.) which ordinarily don't elide >> such. > *shudder* In en_US, maybe... I'm an en_US speaker and pronounce the "h", fwiw. -- Russ Allb

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread Steve McIntyre
The Wanderer wrote: >On 2017-04-14 at 09:34, Wouter Verhelst wrote: >> >> Yes, you're right of course. I was thinking of a specific example >> (don't remember which one anymore) where the word was *written* with >> an H at the start, but the H was not pronounced; I just wrote it >> down incorrectl

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread Graham Inggs
On 14 April 2017 at 17:06, Jonas Smedegaard wrote: > Quoting The Wanderer (2017-04-14 15:46:53) >> At a guess, probably "herb", which is commonly pronounced without the >> initial aspirant even in dialects (etc.) which ordinarily don't elide >> such. > > Thanks for educating me: I thought the "h"

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread Jonas Smedegaard
Quoting The Wanderer (2017-04-14 15:46:53) > On 2017-04-14 at 09:34, Wouter Verhelst wrote: > > > On Thu, Apr 13, 2017 at 10:13:40AM +0300, Lars Wirzenius wrote: > > > >> On Thu, Apr 13, 2017 at 08:59:30AM +0200, Wouter Verhelst wrote: > > >>> (or the letter h followed by a vowel) > >> > >> A h

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread The Wanderer
On 2017-04-14 at 09:34, Wouter Verhelst wrote: > On Thu, Apr 13, 2017 at 10:13:40AM +0300, Lars Wirzenius wrote: > >> On Thu, Apr 13, 2017 at 08:59:30AM +0200, Wouter Verhelst wrote: >>> (or the letter h followed by a vowel) >> >> A hat, a hotel. a helmet. Unless the speaker has a dialect where

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-14 Thread Wouter Verhelst
gt; > > Subject: Re: Bug#860170: node-brfs -- browserify fs.readFileSync() > > > > static asset inliner > > > > > > This should have "ITP" in the title of the bug. > > Best achieved by using reportbug, which gets all the detail

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-13 Thread Lars Wirzenius
On Thu, Apr 13, 2017 at 08:59:30AM +0200, Wouter Verhelst wrote: > On Wed, Apr 12, 2017 at 10:16:18PM +0100, Jonathan Dowland wrote: > > On Wed, Apr 12, 2017 at 03:35:46PM +0200, Bastien ROUCARIES wrote: > > > Subject: Re: Bug#860170: node-brfs -- browserify fs.readFileSync() s

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-13 Thread Wouter Verhelst
On Wed, Apr 12, 2017 at 10:16:18PM +0100, Jonathan Dowland wrote: > On Wed, Apr 12, 2017 at 03:35:46PM +0200, Bastien ROUCARIES wrote: > > Subject: Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static > > asset inliner > > This should have "IT

Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static asset inliner

2017-04-12 Thread Jonathan Dowland
On Wed, Apr 12, 2017 at 03:35:46PM +0200, Bastien ROUCARIES wrote: > Subject: Re: Bug#860170: node-brfs -- browserify fs.readFileSync() static > asset inliner This should have "ITP" in the title of the bug. > Browserify is an JavaScript tool (compiler) tha