on Sat, 09 Nov 2002 05:21:16PM -0500, Stephen Gran insinuated:
> I have it mostly working the way I want (as you can see by the .sig
> below), but it's not yet maintenance free. The right column is
> fortune -s | fold -sw 48, but fold doesn't always deal with line breaks
> as expected, and leaves
Hello all,
Sorry to be so off-topic, but I'm sure many of you use signify, and I'm
having a little trouble getting it to do exactly what I want.
I have it mostly working the way I want (as you can see by the .sig
below), but it's not yet maintenance free. The right column is
fo
on Wed, May 01, 2002, Karl E. Jorgensen ([EMAIL PROTECTED]) wrote:
> On Wed, May 01, 2002 at 11:42:56AM -0700, Karsten M. Self wrote:
> > on Wed, May 01, 2002, Sam Varghese ([EMAIL PROTECTED]) wrote:
> > > How does one set random signatures in mutt after compilation? I
ly be done by editing config.h during compilation.
> > Is there some hack for this? I'm running version 1.3.28i on Woody.
>
> Signify here.
>
> After having some stunningly good luck with advertising a number of
> causes (including my resume) over the past couple
ly be done by editing config.h during compilation.
> > Is there some hack for this? I'm running version 1.3.28i on Woody.
>
> Signify here.
>
> After having some stunningly good luck with advertising a number of
> causes (including my resume) over the past couple
I'm running version 1.3.28i on Woody.
Signify here.
After having some stunningly good luck with advertising a number of
causes (including my resume) over the past couple of years, I'm plugging
a number of causes (or broadcasting pans) with Signify. Highly
recommended Googlebombing
Hi,
I'm setting up a signature file for use with the signify program.
I noticed that when a signature includes the $, signify tries to
expand it as a variable name. I tried using \$, but that didn't
work. Aparently it's a 'perl' thing. Could somebody enlighten m
On Sat, 28 Feb 1998, Brian White wrote:
> > My signify signature's, when used with pine sometimes die completely, and
> > I am completely frustrated :) And to top it all off, I only sometimes get:
> >
> > [1]+ Broken pipe signify --fifo=$HOME/.signatur
> My signify signature's, when used with pine sometimes die completely, and
> I am completely frustrated :) And to top it all off, I only sometimes get:
>
> [1]+ Broken pipe signify --fifo=$HOME/.signature
>
> I suppose I should mention that I use the fifo opt
My signify signature's, when used with pine sometimes die completely, and
I am completely frustrated :) And to top it all off, I only sometimes get:
[1]+ Broken pipe signify --fifo=$HOME/.signature
I suppose I should mention that I use the fifo option...
Has anyone had some
On Sun, Feb 01, 1998 at 07:40:26PM +1000, Anthony Towns wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
>
> On Sun, 1 Feb 1998, Branden Robinson wrote:
>
> > I tried to implement these solutions using the start-stop-daemon, but I
> > encountered a number of difficulties with that approach, not the
I'll create a section called "Debian Tips" in faqomatic, and put this as the
first one to start it all :-).
Sounds good?
--
Proudly running Debian Linux! Linux vs. Windows is a no-Win situation
Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED]
--
TO UNSUBSCRI
On Sun, 1 Feb 1998, Branden Robinson wrote:
> Here's a couple of tricks I worked up for using fetchmail and signify as
> daemons. Put these in your .login or .profile .
>
> First, I wanted to make sure fetchmail was running; answer, just run it
> from the .login, right?
-BEGIN PGP SIGNED MESSAGE-
On Sun, 1 Feb 1998, Branden Robinson wrote:
> I tried to implement these solutions using the start-stop-daemon, but I
> encountered a number of difficulties with that approach, not the least of
> which was that the "--help" option lied to me; if you give
> star
Here's a couple of tricks I worked up for using fetchmail and signify as
daemons. Put these in your .login or .profile .
First, I wanted to make sure fetchmail was running; answer, just run it
from the .login, right? But I didn't want to bitch about "waking up" to
grab mail
> Does anybody know how to use signify with pine? I've copied one example
> as my .signify in my $HOME dir., but I'm clueless on how to make it work
> with pine.
The easiest way to do this is to add a command like
sh -c "signify --fifo=$HOME/.signature &&quo
If signify is the one that uses a fifo for .signature, I tried that and it
worked fine. Doing a cat .signature generated different signatures each
time. Pine didn't like it at all.
On Fri, 8 Aug 1997, Michael B. Taylor wrote:
> >
> > Does anybody know how to use signify with p
>
> Does anybody know how to use signify with pine? I've copied one example
> as my .signify in my $HOME dir., but I'm clueless on how to make it work
> with pine.
Try .signature
Mike
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
-BEGIN PGP SIGNED MESSAGE-
Does anybody know how to use signify with pine? I've copied one example
as my .signify in my $HOME dir., but I'm clueless on how to make it work
with pine.
TIA.
-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: noconv
iQCV
> I start signify with the following command:
> signify --fifo=$HOME/.signature &
>
> This allows me to at least get to the "compose" screen in pine. Oddly
> there is no sig presented, and signify then dies with the following error
> to the tty that I started
Hi folks,
Its a small thing, but its been bugging me for awhile now.
I start signify with the following command:
signify --fifo=$HOME/.signature &
This allows me to at least get to the "compose" screen in pine. Oddly
there is no sig presented, and signify then dies with the foll
21 matches
Mail list logo
