Alexander Skwar <[EMAIL PROTECTED]> writes:
> To GC: I can really understand you well! I'm also fed up with this quoting
> style (cf. Newbie mailing list, 1-2 weeks ago, thread: Text goes on top)
> (actually, David is the wrong person to barf at. He's doing very fine, at
> least compared to ma
On Wed, Jul 26, 2000 at 04:26:48PM -0700, Anton Graham wrote:
> Submitted 26-Jul-00 by David Walluck:
> > But as I understand Mutt is no better at this.
>
> Mutt allows you to use any editor you wish, but defaults to vi.
No, it doesn't default to vi IIRC. It conforms to the general standard,
wh
On Wed, Jul 26, 2000 at 07:17:19PM -0400, David Walluck wrote:
> I guess you have never used pico :) You should just to see that it has 12
> commands. That is *it*. But as I understand Mutt is no better at this. But
> you will never trully understand how hard it is with pico until you've
> tried i
Submitted 26-Jul-00 by David Walluck:
> But as I understand Mutt is no better at this.
Mutt allows you to use any editor you wish, but defaults to vi.
Personally I use Jed as my editor for composing emails.
--
_
_|_|_
( ) *Anton Graham
/v\ / <[EMAIL PROTECTED]
On 27 Jul 2000, Guillaume Cottenceau wrote:
> David Walluck <[EMAIL PROTECTED]> writes:
>
> Also, if you want to go at the very bottom your editor should provide a
> shortcut.
I guess you have never used pico :) You should just to see that it has 12
commands. That is *it*. But as I understand M
David Walluck <[EMAIL PROTECTED]> writes:
> On 26 Jul 2000, Guillaume Cottenceau wrote:
>
> > "Thomas M. Beaudry" <[EMAIL PROTECTED]> writes:
> >
> > > My sentiments exactly. Back when I started, correct netiquette was to put your
> > > reply at the top so people didn't have to scroll down loo
David Walluck <[EMAIL PROTECTED]> writes:
> OK, first let me say that I think your posts amount to a flame. This is
No I'm sorry this is not a flame. This is a fedup because many people are
not respecting "commonly agreed netiquette", and that makes me waste time
(and more important, miss import
David Walluck <[EMAIL PROTECTED]> writes:
>
> I hope all this is not an attempt to get me to switch to gnus. In fact, I
> read the gnus HOWTO on your site a couple days ago, and though I'd like to
> try it... emacs has far too many sortcuts for me to remember! Then again
> vi is bad about that,
On 26 Jul 2000, Guillaume Cottenceau wrote:
> "Thomas M. Beaudry" <[EMAIL PROTECTED]> writes:
>
> > My sentiments exactly. Back when I started, correct netiquette was to put your
> > reply at the top so people didn't have to scroll down looking for it.
>
> Complete nonsense! If you want to not
On 26 Jul 2000, Guillaume Cottenceau wrote:
> No, if it's a general reply you should remove everything (the good
> version) (because every good mailer as a thread option that enables the
> look of the original message), or leave everything and reply at the bottom
> (because when I want to read th
Francis Galiegue <[EMAIL PROTECTED]> writes:
> On 26 Jul 2000, Guillaume Cottenceau wrote:
>
> >
> > (Please, pine/mutt/etc lovers, use quick and efficient arguments if you
> > really feel this is the place for a mailreader flame) (my point is just to
> > propose ONE tool to ease the efficiency
Francis Galiegue <[EMAIL PROTECTED]> writes:
> and pine is truly lightweight.
but pine is not free :-(
of your emails).
> >
>
> OK, lets troll: pine + vim as alternate editor rocks. No best
> editor than vim
> and pine is truly lightweight.
>
yep, just have to love vi, i set it as my default editor for /usr/bin/Mail
...
> --
> Francis Galiegue, [EMAIL PROTECTED]
> "Programming is a race betw
On 26 Jul 2000, Guillaume Cottenceau wrote:
>
> (Please, pine/mutt/etc lovers, use quick and efficient arguments if you
> really feel this is the place for a mailreader flame) (my point is just to
> propose ONE tool to ease the efficiency and quality of your emails).
>
OK, lets troll: pine + v
David Walluck <[EMAIL PROTECTED]> writes:
> On 25 Jul 2000, Guillaume Cottenceau wrote:
>
> > David Walluck <[EMAIL PROTECTED]> writes:
> >
> > PS : please quote your answer the right way, e.g. put answers *after*
> > questions..
>
> Are you talking about where I put my reply? It normally come
David Walluck <[EMAIL PROTECTED]> writes:
> On 25 Jul 2000, Guillaume Cottenceau wrote:
>
> > PS : please quote your answer the right way, e.g. put answers *after*
> > questions..
>
> What?
Your original message was:
It's good for newbies, but should be extended to expert or developer
sectio
"Thomas M. Beaudry" <[EMAIL PROTECTED]> writes:
> My sentiments exactly. Back when I started, correct netiquette was to put your
> reply at the top so people didn't have to scroll down looking for it.
Complete nonsense! If you want to not quote, please DON'T include the
original message in your
On 25 Jul 2000, Guillaume Cottenceau wrote:
> David Walluck <[EMAIL PROTECTED]> writes:
>
> PS : please quote your answer the right way, e.g. put answers *after*
> questions..
Are you talking about where I put my reply? It normally comes after the
section I am talking about, but if I just hit "
As it was back then. Never email when you're half asleep.
On Wed, 26 Jul 2000, Alexander Skwar wrote:
> Don't know about back then, but nowadays you only quote as much as needed
On Wed, Jul 26, 2000 at 03:57:37AM -0400, Thomas M. Beaudry wrote:
> My sentiments exactly. Back when I started, correct netiquette was to put your
> reply at the top so people didn't have to scroll down looking for it.
Don't know about back then, but nowadays you only quote as much as needed
(i
My sentiments exactly. Back when I started, correct netiquette was to put your
reply at the top so people didn't have to scroll down looking for it.
On Tue, 25 Jul 2000, you wrote:
> On 25 Jul 2000, Guillaume Cottenceau wrote:
>
> > PS : please quote your answer the right way, e.g. put answers
On 25 Jul 2000, Guillaume Cottenceau wrote:
> PS : please quote your answer the right way, e.g. put answers *after*
> questions..
What?
--
Sincerely,
David Walluck
<[EMAIL PROTECTED]>
David Walluck <[EMAIL PROTECTED]> writes:
> It's good for newbies, but should be extended to expert or developer
> sections... i.e RPM-HOWTO, how to make an ISO, how to mirror, how to keep
> up-to-date... a lot of stuff the cooker website has but in much more
> detail as it is a FAQ and FAQ's alw
It's good for newbies, but should be extended to expert or developer
sections... i.e RPM-HOWTO, how to make an ISO, how to mirror, how to keep
up-to-date... a lot of stuff the cooker website has but in much more
detail as it is a FAQ and FAQ's always have great explanations for the
questions for s
On Tue, Jul 25, 2000 at 06:02:56PM +0200, Guillaume Cottenceau wrote:
> Hence, we (Geoffrey Lee, Guillaume Cottenceau) have decided on the idea of
> the "Cooker-FAQ" which will be available:
Good idea! I like it.
Alexander Skwar
--
Homepage: http://www.digitalprojects.com
Sichere Mail?
Hello fellow cookers, :-)
The cooker list is a place to discuss the latest cooker distribution,
while this can allow developpers to interact closely with Mandrake users,
it also means that there may be users screaming to get things fixed,
discussing what to do with broken packages, and developper
26 matches
Mail list logo