Pterodactyl Gnus v0.39 is released

Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Bug fixes and new things.

Get it from <URL:http://www.gnus.org/pgnus.tar.gz> or
"/ftp@ftp.gnus.org:/pub/emacs/gnus/".  The patch is available as
<URL:http://www.gnus.org/patches/pgnus-0.38-0.39.diff.gz>.

ChangeLog since last release:

Sun Oct 25 06:23:13 1998  Lars Magne Ingebrigtsen  <larsi@menja.ifi.uio.no>

	* gnus.el: Pterodactyl Gnus v0.39 is released.

1998-10-25 00:34:39  Lars Magne Ingebrigtsen  <larsi@gnus.org>

	* gnus-art.el (gnus-ignored-mime-types): New variable.
	(gnus-mime-display-single): Use it.
	(gnus-treatment-function-alist): New variable.

	* gnus.el (gnus-mime): New group.

	* gnus-art.el (gnus-mime-display-alternative): Don't destroy
	things for other parts.
	(gnus-mime-display-alternative): Place point.

	* gnus.el: autoload gnus-uu-post-news.

	* mailcap.el (mailcap-mailcap-entry-passes-test): Also check
	needsterm/DISPLAY. 

	* mm-decode.el (mm-display-part): Default to inline text/.*
	parts. 

	* mm-bodies.el (mm-decode-content-transfer-encoding): Default to
	8bit. 

	* gnus-art.el (gnus-mime-copy-part): Use normal-mode.
	(gnus-mime-display-single): Inline all text parts.
	(gnus-article-narrow-to-signature): Removed mime:: stubs.

1998-10-24 21:38:37  Lars Magne Ingebrigtsen  <larsi@gnus.org>

	* nnml.el (nnml-possibly-create-directory): Rewrite.
	(nnml-request-create-group): Change to right server.

	* gnus-xmas.el (gnus-xmas-define): Use byte-code-function-p. 

	* gnus-sum.el (gnus-set-mode-line): Use truncate-string-to-width. 

	* gnus.el: rmail-output-to-rmail-file autoload.

	* gnus-util.el (gnus-output-to-rmail): Didn't work if not in
	Gnus. 

	* nnheader.el (nnheader-parse-head): Checked wrong variable.

	* gnus-sum.el (gnus-summary-update-mark): Ignore nil'd marks.

Tue Oct 20 23:37:43 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* gnus-art.el (gnus-mime-display-mixed): Multipart in
	mixed part.

Tue Oct 20 23:36:43 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* gnus-sum.el (gnus-summary-exit): Use mm-destroy-parts.
	
	* gnus-sum.el (gnus-summary-exit-no-update): Ditto.

Tue Oct 20 16:22:51 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* mm-uu.el (mm-uu-dissect): Create pseudo multipart head.

1998-10-24 20:51:53  Lars Magne Ingebrigtsen  <larsi@gnus.org>

	* gnus-sum.el (gnus-valid-move-group-p): Make sure group has a
	value. 

	* gnus-art.el (gnus-article-hidden-text-p): Return nil when not
	hidden. 

	* gnus-spec.el (gnus-update-format-specifications): Use the
	article mode line spec.

	* gnus-art.el (gnus-insert-mime-button): Put right type.
	(gnus-insert-prev-page-button): Ditto.
	(gnus-insert-next-page-button): Dutti.

	* pop3.el: New version installed.

Sat Oct 24 16:48:51 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* mm-uu.el (mm-uu-dissect): Delete the begining spurious newline
	and display last part.



-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Shenghuo ZHU]

Three releases one+ day. Great!

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

LMI> 1998-10-25 00:34:39  Lars Magne Ingebrigtsen  <larsi@gnus.org>

LMI> 	* gnus-art.el (gnus-ignored-mime-types): New variable.
LMI> 	(gnus-mime-display-single): Use it.
LMI> 	(gnus-treatment-function-alist): New variable.

(defvar gnus-treatment-function-alist ()
  '((gnus-treat-body-highlight-signature gnus-article-highlight-signature nil)
    ))

It seems not correct.

-- 
Shenghuo

Re: Pterodactyl Gnus v0.39 is released

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> 	* gnus-xmas.el (gnus-xmas-define): Use byte-code-function-p.

Huh?!  Why?  byte-code-function-p is an obsolete function that should
not be used.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Which is worse: ignorance or apathy?  Who knows?  Who cares?

Re: Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> (defvar gnus-treatment-function-alist ()
>   '((gnus-treat-body-highlight-signature gnus-article-highlight-signature nil)
>     ))
> 
> It seems not correct.

Well, it is correct, but it's not finished.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> Huh?!  Why?  byte-code-function-p is an obsolete function that should
> not be used.

It is?  Under Emacs 20.3 compiled-function-p is the obsolete function
that should not be used.  :-)

You should coordinate this with RMS.

(Actually, I think byte-code-function-p makes more sense, in case we
later get natively compiled functions, which would then be, like,
compiled-function-p'd functions.  Or perhaps they would just be
subrs?) 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> It is?  Under Emacs 20.3 compiled-function-p is the obsolete function
> that should not be used.  :-)

Yes, but in the file named `gnus-xmas.el' it would be nice to use the
XEmacsish functions.  Perhaps that's the XEmacs developer in me
talking.

> You should coordinate this with RMS.

I don't see what's there to coordinate.  The object is named
`compiled-function', so the predicate is `compiled-function-p'.  Like
bufferp or framep or whatever.  And this isn't anything new --
compiled functions have been there since at least 19.12.  Besides, I
think Common Lisp also has compiled-function-p.

> (Actually, I think byte-code-function-p makes more sense, in case we
> later get natively compiled functions, which would then be, like,
> compiled-function-p'd functions.

If they compile into compiled-function objects, compiled-function-p
will return t on them.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
aibohphobia (ay' bo fo beeya): n. The fear of palindromes.

Re: Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> Yes, but in the file named `gnus-xmas.el' it would be nice to use the
> XEmacsish functions.  Perhaps that's the XEmacs developer in me
> talking.

:-)

I've changed gnus-xmas back.

> > You should coordinate this with RMS.
> 
> I don't see what's there to coordinate.  The object is named
> `compiled-function', so the predicate is `compiled-function-p'.  Like
> bufferp or framep or whatever.

Perhaps the object should be `byte-code-function' instead?

> And this isn't anything new -- compiled functions have been there
> since at least 19.12.  Besides, I think Common Lisp also has
> compiled-function-p.

Yes, but in CL this is true for functions that really are compiled,
and not just byte-compiled.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > I don't see what's there to coordinate.  The object is named
> > `compiled-function', so the predicate is `compiled-function-p'.  Like
> > bufferp or framep or whatever.
> 
> Perhaps the object should be `byte-code-function' instead?
> 
> > And this isn't anything new -- compiled functions have been there
> > since at least 19.12.  Besides, I think Common Lisp also has
> > compiled-function-p.
> 
> Yes, but in CL this is true for functions that really are compiled,
> and not just byte-compiled.

I disagree with your distinction of "really compiled" vs.
"byte-compiled" functions.  It makes as much sense for compiled
functions to be called just that.  The type of the compilation is an
implementation detail.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Which is worse: ignorance or apathy?  Who knows?  Who cares?

Re: Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> I disagree with your distinction of "really compiled" vs.
> "byte-compiled" functions.  It makes as much sense for compiled
> functions to be called just that.  The type of the compilation is an
> implementation detail.

I don't think so.  The difference between Lisp and byte-code is in
many ways as big as the difference between byte-code and native code.
For instance, you can instrument byte-compiled functions, but you
can't instrument natively compiled code.  You can inspect many things
inside byte-compiled code; you can't do that with native code.  You
can get understandable backtraces with errors in byte-compiled code;
do don't with native code.  Byte-compiled code can't segfault on you;
native code can.  Etc.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> > I disagree with your distinction of "really compiled" vs.
> > "byte-compiled" functions.  It makes as much sense for compiled
> > functions to be called just that.  The type of the compilation is an
> > implementation detail.
> 
> I don't think so.  The difference between Lisp and byte-code is in
> many ways as big as the difference between byte-code and native code.
> For instance, you can instrument byte-compiled functions, but you
> can't instrument natively compiled code.

This statement, as it stands, is untrue for a bunch of Common Lisp
compilers.  For example, CMUCL can instrument natively compiled code,
if you use a debug compiler setting.  I was told the same is true for
ACL.  Also, it's not entirely true that byte-compiled code can't
segfault, etc.

But these things are not the point.  The point is that the crucial
difference (IMHO) is whether the code is interpreted or compiled, not
how it is compiled.  I don't buy the notion that a byte-compiled
function is somehow "less compiled" because it's not compiled to
native code.

So, the moment XEmacs developers decided to abstract away a "compiled
function" object, I believe they chose a good name for the accessor
functions.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
there's a beast upon my shoulder / and a fiend upon my back

Re: Pterodactyl Gnus v0.39 is released

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> But these things are not the point.  The point is that the crucial
> difference (IMHO) is whether the code is interpreted or compiled, not
> how it is compiled.

I agree totally.  And byte-compiled code is interpreted, so the
important distinction here is Lisp/byte-code on the one hand, and
native code on the other.  :-)

> I don't buy the notion that a byte-compiled function is somehow
> "less compiled" because it's not compiled to native code.

Well -- it *is* less compiled.  

> So, the moment XEmacs developers decided to abstract away a "compiled
> function" object, I believe they chose a good name for the accessor
> functions.

And to me it's a nice example of an abstraction that obscures what the
reality is.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Pterodactyl Gnus v0.39 is released

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > I don't buy the notion that a byte-compiled function is somehow
> > "less compiled" because it's not compiled to native code.
> 
> Well -- it *is* less compiled.
> 
> > So, the moment XEmacs developers decided to abstract away a "compiled
> > function" object, I believe they chose a good name for the accessor
> > functions.
> 
> And to me it's a nice example of an abstraction that obscures what
> the reality is.

We are clearly arguing taste here, because I cannot fathom how the
name `compiled-function-p' obscures reality.  To me byte-compilation
is just a form of compilation.  But I'm beginning to repeat myself, so
I guess we'll have to agree to disagree on this.  Or something.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
If we get involved in a nuclear war, will the electromagnetic pulses
from exploding bombs damage my videotapes?

Re: Pterodactyl Gnus v0.39 is released

[Kai Grossjohann]

>>>>> Hrvoje Niksic <hniksic@srce.hr> writes:

  > But these things are not the point.  The point is that the crucial
  > difference (IMHO) is whether the code is interpreted or compiled, not
  > how it is compiled.  I don't buy the notion that a byte-compiled
  > function is somehow "less compiled" because it's not compiled to
  > native code.

I didn't see the beginning of the thread, but IMVHO byte-code is both
compiled and interpreted.

kai
-- 
Life is hard and then you die.

Ignored MIME types!

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> 1998-10-25 00:34:39  Lars Magne Ingebrigtsen  <larsi@gnus.org>
> 
> 	* gnus-art.el (gnus-ignored-mime-types): New variable.

Could we please have this default to nil?  I know vcards are ugly and
useless, but it's scary to just have them *ignored* by default, no
matter how yucky they are.  It took me some time to debug why the
vcard attachment wasn't shown at all.  :-(

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Old numerical analysts never die, they just get disarrayed.

Re: Ignored MIME types!

[Wes Hardaker]

>>>>> On 26 Oct 1998 14:00:59 +0100, Hrvoje Niksic <hniksic@srce.hr> said:

>> * gnus-art.el (gnus-ignored-mime-types): New variable.

Hrvoje> Could we please have this default to nil?  I know vcards are
Hrvoje> ugly and useless, but it's scary to just have them *ignored*
Hrvoje> by default, no matter how yucky they are.  It took me some
Hrvoje> time to debug why the vcard attachment wasn't shown at all.
Hrvoje> :-(

Seconded.  Even if I don't want to see them, I don't think the mail
reader should delete parts of a mail message by default.

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."

Re: Ignored MIME types!

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> > 	* gnus-art.el (gnus-ignored-mime-types): New variable.
> 
> Could we please have this default to nil? 

Yup.  Fix in Pterodactyl Gnus v0.41.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Ignored MIME types!

[Robert Bihlmeyer]

Hi,

>>>>> On 26 Oct 1998 07:58:39 -800
>>>>> Wes Hardaker <wjhardaker@ucdavis.edu> said:

>>>>> On 26 Oct 1998 14:00:59 +0100, Hrvoje Niksic <hniksic@srce.hr> said:

 Hrvoje> I know vcards are ugly and useless, but it's scary to just
 Hrvoje> have them *ignored* by default, no matter how yucky they are.

 Wes> Seconded. Even if I don't want to see them, I don't think the
 Wes> mail reader should delete parts of a mail message by default.

Thirded. (?) I have to see them so I can complain <eg>.

	Robbe

-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>