Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

2017-08-03 Thread Glenn Morris
Eli Zaretskii wrote:

>> Info-default-directory-list, which is the thing that stats the
>> filesystem, is autoloaded.
>
> But who loads it?

Autoloaded variables are dumped with Emacs.



Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

2017-08-03 Thread Glenn Morris
Eli Zaretskii wrote:

>> >2. Why on earth is emacs checking the info path at all on startup?
>
> It doesn't do that here, not in the current development sources.
> After I start "emacs -Q", (featurep 'info) evaluates to nil and
> Info-directory-list is unbound.

Info-default-directory-list, which is the thing that stats the
filesystem, is autoloaded.

This area seems overly complicated, probably due to hysterical raisins.
IIRC we've discussed it before.

>> >3. The documentation talks about setting INFOPATH in the environment
>> >   to over-ride the use of this default directory list, but again
>> >   using strace I can see no change to behaviour here at all if I set
>> >   INFOPATH

The default still gets set, just not used. You might wonder, why bother
setting something that's not used...


Ideally Info-default-directory-list would go away. leaving only
Info-directory-list initialized in a standard fashion. But I haven't
looked at the details.



Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

2017-08-03 Thread Glenn Morris
Steve McIntyre wrote:

> I've checked yesterday using emacs25 (version 25.1+1-4 in Debian
> stretch). I guess those changes didn't make it in before that release

Indeed not.



Bug#786707: bug#27933: emacs25: default info dir initialization slow with remote filesystems

2017-08-03 Thread Glenn Morris

Presumably this is less bad since some changes in Emacs master.
See 8ff9c4109fd and 2a2c6ee8d18.

http://lists.gnu.org/archive/html/emacs-diffs/2016-05/msg00336.html
http://lists.gnu.org/archive/html/emacs-diffs/2016-05/msg00338.html



Bug#730593: bug#18675: Bug#730593: emacs24: fails to set fullscreen frame parameter on gnome 3

2014-10-10 Thread Glenn Morris
martin rudalics wrote:

  (set-frame-parameter nil 'fullscreen 'fullboth)
[...]
 (set-frame-parameter nil 'fullscreen 'maximized)

I see the issue with 24.3 under Gnome on current Debian testing, but the
current pretest, 24.3.94, works fine with either form, with no need for
any other settings. So it seems to be a solved problem.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#597255: bug#597255

2010-09-21 Thread Glenn Morris

BTW, I did not post here owing to the refusal to fix

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63995

but I see my address got posted anyway (3 times). :(

(Not a huge deal, never mind.)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#588859: encode_rfc1522 fails to take into account parentheses

2010-07-12 Thread Glenn Morris
Package: debbugs
Severity: important

We had someone sending mail to debbugs.gnu.org who found his mails
were never appearing on the bug list (ie the maintainer address).
Examining the logs, the gnu.org mail server was rejecting the mails
resent from debbugs with 550 Invalid address in message header.

This appears to be due to a bug in the encode_rfc1522 function.
You can see examples of the input at:

http://debbugs.gnu.org/cgi/bugreport.cgi?msg=19;mbox=yes;bug=6607

and the output at:

http://debbugs.gnu.org/cgi/bugreport.cgi?msg=18;mbox=yes;bug=6607


Debbugs appears to be construcing bad From, Resent-From headers,
violating this section of RFC1522:

   section 5 (Use of encoded-words in message headers):

   (2) An encoded-word may appear within a comment delimited by ( and
   ), i.e., wherever a ctext is allowed.  More precisely, the
   RFC 822 ABNF definition for comment is amended as follows:

   comment = ( *(ctext / quoted-pair / comment / encoded-word) )

   A Q-encoded encoded-word which appears in a comment MUST NOT
   contain the characters (, ) or  encoded-word that appears in
   a comment MUST be separated from any adjacent encoded-word or
   ctext by linear-white-space.


A minimal example that shows the problem is included below:


#!/usr/bin/perl

use strict;
use warnings;

use Debbugs::MIME qw(decode_rfc1522 encode_rfc1522);

my $str = 'n...@example.com (J =?utf-8?Q?Bockg=C3=A5rd?=)';
my $dec = decode_rfc1522($str);
my $enc = encode_rfc1522($dec);

print $str, \n;  # - n...@example.com (J =?utf-8?Q?Bockg=C3=A5rd?=)
print $dec, \n;  # - n...@example.com (J Bockgård)
print $enc, \n;  # - n...@example.com (J =?UTF-8?Q?Bockg=C3=A5rd)?=




(I don't want my email unobscured on the web, so the from address is
hopefully faked. I will read any responses via the web interface.)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#418110: documentation at top of pcomplete.el should not tell users to (load pcmpl-auto)

2007-04-06 Thread Glenn Morris
Jason Spiro wrote:

 Remove the line
 ;;   (load pcmpl-auto)
 from the top-of-file comments; just (add-hook 'shell-mode-hook
 'pcomplete-shell-setup) works fine on its own.

Corrected, thanks.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]