public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Probably a simple pine question...
Date: Mon, 25 Jul 2005 17:36:50 -0600 (Mountain Daylight Time)	[thread overview]
Message-ID: <Pine.WNT.4.63.0507251732550.1680@merlin> (raw)
In-Reply-To: <Pine.WNT.4.63.0507251716580.1680@merlin>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I forgot, if you want to use that feature regularly, you may want to add
it to the default-composer-hdrs list. You would set it to this value if
all you want is to add the Bcc header.

To:, Cc:, Bcc:, Attchmnt:, Subject:

You must specify all of them if you set this.

- --
It's not one damn thing after another, it's the same damn thing over and
over. (History repeats itself)
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7

And so it came to pass that on Mon, 25 Jul 2005, Joseph C. Lininger said

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> While in the headers, press ctrl+R to show full headers. Then, bcc
will
> be included in the list.
>
> - --
> It's not one damn thing after another, it's the same damn thing over
and
> over. (History repeats itself)
> Joseph C. Lininger
> jbahm@pcdesk.net
> Verification: 5eab38a77ac40416e075be8f50607ff7
>
> And so it came to pass that on Mon, 25 Jul 2005, Dan Murphy said
>
>> I was just about to send something here, and I discovered I didn't
> know how
>> to do BCC in Pine.
>> so like how do you do that?
>> Thanks
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
>
> iD8DBQFC5XMPJ6dqn0mqPbARAqoqAJ0Zil/0syp97FqQhVLQOuKmjxmN+QCeKA6a
> +tvRx6Sm62w2WSMs6sHQ/QE=
> =j8RL
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFC5XeZJ6dqn0mqPbARAqtoAKC1yMBrpaFZ5xJJmgREPLGiYi9iWgCglzy0
JwtFntmMAuu+EuxBIYroC+A=
=DwVN
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Dan Murphy
 ` Charles Hallenbeck
 ` Joseph C. Lininger
   ` Joseph C. Lininger [this message]
     ` Dan Murphy
   ` Dan Murphy

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.WNT.4.63.0507251732550.1680@merlin \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).