Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: Removed forward slash?
Date: 17 Jul 1999 11:22:23 -0400	[thread overview]
Message-ID: <oqpv1re1xs.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Harry Putnam's message of "17 Jul 1999 07:22:18 -0700"

Harry Putnam <reader@newsguy.com> écrit:

> However, looking through the material at the node suggested [`Article
> Fontisizing'] I discovered no clue as to which thing should be set to
> "nil" to stop this from happening.  "s" searches on "italic" or "forward
> slash" were no more helpful.

Let me see.  The quoted node immediately speaks about `gnus-emphasis-alist',
which you may modify.  As it makes it pretty clear that Lars calls
`emphasis' the set of phenomena it describes, you might have searched on
`emphasis' and been more successful...  The node also contains a clear
`*Note' pointing to the `Customizing Articles' node, and in that node,
you find the variable `gnus-treat-emphasize', preceded by an explanation
of possible values.  Are you sure you were really seeking for clues? :-)

> I think I'd prefer to have gnus leave things alone that I purposely
> type in to be seen.

The problem is that we may have /varying/ purposes.  For example, in the
previous sentence, I put "varying" between slashes with the purpose that
you will see it italicised. :-)

> Further it seems that this `forward slash removal' thing should default
> to nil to begin with.  Users who want special handling of strings
> inclosed in forward slashes can figure out how to do it.

Asterisks and underline symbols are also usable for emphasis, and disappear
the same way.  On average, people are happy with the current behaviour.
Those are all rather unusual characters in prose, the current behaviour may
be acceptable.  In any case, we are free to turn it on or off by changing
the value of `gnus-treat-emphasize', if the default does not suit us.

> Many situations require forward slashes.  Especially in mail about
> computer use or unix utils. To be able to "see" what you've typed into
> a message shouldn't require lengthy info searches.

Nothing is perfect, you know.  Email is not necessarily about computers,
even if true that for us, it traditionnaly is.  I prefer having to mentally
restore invisible slashes around unexpected italics in a file path name,
rather occasionally, than to execute Gnus command to emphasize on demand,
all the time.  Many of my correspondents emphasise a lot, or regularly.
I prefer to see me (and us :-) more prose-oriented than computer-oriented.
Like dogs do after a shower, let's shake out all this dust of bits we have
on ourselves! :-)

One alternative is that we all start using `text/enriched' text more often
than we do now, but Lars does not much believe it is practical to aim such
a thing, at least from the last time we spoke about it.  I would guess he
is not be completely wrong on this one :-) :-).


P.S. - By the way, the French readers on this list might be amused to know
that `forward slash' is sometimes translated by `cotice' and `backslash' by
`contre-cotice' (I found these as comments within the French translation of
ISO 10646 names).  I like these, and I wish they would become as known as
`perluette' or `arrobas' (yet there are spelling fights about the latter).

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard



  reply	other threads:[~1999-07-17 15:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-17 12:55 Harry Putnam
1999-07-17 13:11 ` François Pinard
1999-07-17 14:22   ` Harry Putnam
1999-07-17 15:22     ` François Pinard [this message]
1999-07-17 16:52       ` Harry Putnam
1999-07-17 17:37       ` Hrvoje Niksic
1999-07-17 18:34         ` François Pinard
1999-07-17 22:46           ` Kai Großjohann
1999-07-21 15:45             ` François Pinard
1999-07-19  5:24         ` Matt Simmons
1999-07-19 10:54           ` Kai Großjohann
1999-07-19 14:54           ` Hrvoje Niksic
1999-07-17 16:48     ` Hrvoje Niksic
1999-07-17 22:32       ` Kai Großjohann
1999-07-19 11:32     ` Toby Speight
1999-08-27 19:31     ` Lars Magne Ingebrigtsen
1999-07-17 16:44   ` Hrvoje Niksic
1999-07-17 17:00     ` Harry Putnam
1999-07-17 22:29       ` Kai Großjohann
1999-07-18 10:07     ` Norman Walsh
1999-07-19 22:32       ` Rui Zhu
1999-07-18 15:38     ` Paul Stevenson
1999-07-19  0:11       ` Stainless Steel Rat
1999-07-19 10:53       ` Kai Großjohann
1999-07-19 14:04         ` Paul Stevenson
1999-07-19 14:36           ` Kai Großjohann
1999-07-19  6:54     ` Thomas Lofgren
1999-07-19  7:37     ` Jaap-Henk Hoepman

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=oqpv1re1xs.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=ding@gnus.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 NNTP newsgroup(s).