[EMAIL PROTECTED] writes:
> Are there any guidelines or anything specific for packaging emacsen
> software? If I can figure out what to do, I might just get off my butt. :)
/usr/share/doc/emacsen-common/debian-emacs-policy.gz, in the
emacsen-common package.
--
"Welcome to the Slippery Slope. Her
Whoah, traffic. :) I'm reminded about updating the tinymud muck client,
which hasn't seen much of an update in the past six-odd years AFAIK.
Are there any guidelines or anything specific for packaging emacsen
software? If I can figure out what to do, I might just get off my butt. :)
On 10 Aug 2
Alex Shinn <[EMAIL PROTECTED]> writes:
> Ben> Alex Shinn <[EMAIL PROTECTED]> writes:
> >> task-emacs would include all the Emacs packages necessary to
> >> use Emacs as your shell/mail client/news reader/etc.
>
> Any of them.
I see.
> Shell comes with every emacsen, so that's not re
> "Ben" == Ben Pfaff <[EMAIL PROTECTED]> writes:
Ben> Alex Shinn <[EMAIL PROTECTED]> writes:
>> task-emacs would include all the Emacs packages necessary to
>> use Emacs as your shell/mail client/news reader/etc.
Ben> Necessary to use *which* Emacs as those things?
Any of the
Alex Shinn <[EMAIL PROTECTED]> writes:
> task-emacs would include all the Emacs packages necessary to use Emacs
> as your shell/mail client/news reader/etc.
Necessary to use *which* Emacs as those things?
To further spread the cause of the One True Editor, I was thinking
about making task-emacs and user-emacs packages.
task-emacs would include all the Emacs packages necessary to use Emacs
as your shell/mail client/news reader/etc.
user-emacs would include a script to configure your .emacs to use
6 matches
Mail list logo
