sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: "kim kubik" <chaotrope@jps.net>
To: "kim kubik" <chaotrope@jps.net>, <jim.robinson@stanford.edu>,
	"sam Fans" <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: the obvious. =) (to everyone but kim)
Date: Thu, 30 Mar 2000 20:12:53 -0500	[thread overview]
Message-ID: <01bf9aae$3d654fe0$e6c9efd1@pkwksj.sjna.corp.dom> (raw)

-----Original Message-----
From: James A. Robinson <jim.robinson@stanford.edu>
To: kim kubik <chaotrope@jps.net>
Date: Monday, March 27, 2000 2:55 PM
Subject: Re: the obvious. =) (to everyone but kim) 
      
       (kim wrote):
>> PS: Jim I also have a number of SREs that walk through a file and
>>     delete those little copywrite notices and things like that which
>>     you Elsevier people seem to be so keen on including.     :-)

  (and Jim replied):
> Elsevier??? What gave you the idea I was an Elsevier person?
> I work for HighWire Press, Elsevier is the antithesis of us.
>
> Jim

Ooops, guess I stuck my foot in it again! Sorry if there are
any implications I'm unaware of vis-a-vis Highwire & Elsevier,
like maybe Elsevier publishes only to the pederast trade,
while Highwire has loftier aspirations.

On a safer topic the re you gave for <b>bolding</b> dot in an
html file just needed a  tiny addition to work in (I think, a
dubious activity at best and not equating to 'I am') that

    s/(.+\n*)*/<b>&<\/b>/

will surround any amount of backhilited text with <b>...</b>,
not just text on one line, and the text may include blank lines.

So thank you and sorry about the faux pas.

- kim




             reply	other threads:[~2000-04-03 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-31  1:12 kim kubik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-27 22:39 kim kubik

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='01bf9aae$3d654fe0$e6c9efd1@pkwksj.sjna.corp.dom' \
    --to=chaotrope@jps.net \
    --cc=jim.robinson@stanford.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /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).