Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Gernot Hassenpflug <gernot@coda.ocn.ne.jp>
To: info-gnus-english@gnu.org
Subject: Re: how to obtain green background for some text?
Date: Sun, 22 Jul 2007 01:22:56 +0900	[thread overview]
Message-ID: <871wf1n2u7.fsf@aikishugyo.dnsdojo.org> (raw)
In-Reply-To: <mailman.3701.1184955717.32220.info-gnus-english@gnu.org>

Tom Rauchenwald <its.sec@gmx.net> writes:

> Gernot Hassenpflug <gernot@coda.ocn.ne.jp> writes:
>
>> Hello,
>>
>> I have used boxquote.el a lot for marking cited text, but am searching
>> for a manner in which to mark text, particularly code, in my posting
>> with a green background. Searches for "background color",
>> "highlighting", and similar did not lead to any useful links for me
>> either for this newsgroup or the comp.text.tex group. I am hoping
>> someone here knows how to do this in gnus. I have also tried emacs's
>> text properties from the edit menu, but none of the font
>> foreground/background options are available in editing articles for
>> newsgroups.
>
> I don't quite understand. You can't tell in a usenet-message how
> another client should render your code (unless you use html, but that
> is evil). Do you mean something like the #v+ and #v- marks? If I
> recall correctly, No Gnus supports them, like

Yes, that more or less it. Seems something like that, since whatever
it is you did made me see the line with "code" in green text on a sort
of beige background. I have no idea what you call that: are those #v
things escape sequences? I don't even know what I should be searching
for... when I look at the "raw" article in gnus, or reply, there is
nothing different visible anymore.

I did not know that you canot tell another client these things. For
instance, we have *text* which some readers will interpret as bold
text, or underlined, or something. I haven't seen any documentation in
gnus on that, but assumed it was standard rendering for newsreaders
that can do that (like showing smileys in graphics if they have the
capability).

> code...
>
> But not many clients support this (afaik slrn does).

I see, I am indeed using No Gnus v0.6.

Thanks,
        Gernot
-- 
Gernot Hassenpflug

      parent reply	other threads:[~2007-07-21 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 15:57 Gernot Hassenpflug
2007-07-20 18:21 ` Tom Rauchenwald
2007-07-21 11:09   ` Leo
2007-07-21 11:57     ` Reiner Steib
2007-07-21 16:28       ` Gernot Hassenpflug
2007-07-21 18:08         ` Reiner Steib
2007-07-22  1:53           ` Gernot Hassenpflug
2007-07-22  8:57             ` Reiner Steib
2007-07-22 14:46               ` Gernot Hassenpflug
     [not found] ` <mailman.3701.1184955717.32220.info-gnus-english@gnu.org>
2007-07-21 16:22   ` Gernot Hassenpflug [this message]

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=871wf1n2u7.fsf@aikishugyo.dnsdojo.org \
    --to=gernot@coda.ocn.ne.jp \
    --cc=info-gnus-english@gnu.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).