Debian Bug report logs - #399215
libapache2-mod-php4: Emacs readline problem "What would you like to do about php.ini?"

Package: debconf; Maintainer for debconf is Debconf Developers <[email protected]>; Source for debconf is src:debconf (PTS, buildd, popcon).

Reported by: Jari Aalto <[email protected]>

Date: Sat, 18 Nov 2006 16:18:06 UTC

Severity: normal

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to [email protected], Debian PHP Maintainers <[email protected]>:
Bug#399215; Package libapache2-mod-php4. (full text, mbox, link).


Acknowledgement sent to Jari Aalto <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian PHP Maintainers <[email protected]>. (full text, mbox, link).


Message #5 received at [email protected] (full text, mbox, reply):

From: Jari Aalto <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: libapache2-mod-php4: Emacs readline problem "What would you like to do about php.ini?"
Date: Sat, 18 Nov 2006 18:08:30 +0200
Package: libapache2-mod-php4
Version: 4:4.4.4-7
Severity: normal

While upgrading under Emacs terminal (M-x shell) it reads:

    Setting up php4-common (4.4.4-7) ...
    Setting up libapache2-mod-php4 (4.4.4-7) ...
    debconf: unable to initialize frontend: Dialog
    debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
    debconf: falling back to frontend: Readline
    What would you like to do about php.ini? 

SUGGESTION

- The question presented is not clear. Please print an introductory message explaining
  what is the problem, why the question are asked and what are the choices to the question.
- Please always state all path names in full, like php.ini in this case.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)

Versions of packages libapache2-mod-php4 depends on:
ii  apache2- 2.2.3-3.1                       Traditional model for Apache HTTPD
ii  apache2. 2.2.3-3.1                       Next generation, scalable, extenda
ii  libbz2-1 1.0.3-6                         high-quality block-sorting file co
ii  libc6    2.3.6.ds1-8                     GNU C Library: Shared libraries
ii  libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library
ii  libdb4.4 4.4.20-8                        Berkeley v4.4 Database Libraries [
ii  libexpat 1.95.8-3.3                      XML parsing C library - runtime li
ii  libkrb53 1.4.4-4                         MIT Kerberos runtime libraries
ii  libmagic 4.17-4                          File type determination library us
ii  libpcre3 6.7-1                           Perl 5 Compatible Regular Expressi
ii  libssl0. 0.9.8c-3                        SSL shared libraries
ii  libzzip- 0.12.83-8                       library providing read access on Z
ii  mime-sup 3.37-1                          MIME files 'mime.types' & 'mailcap
pn  php4-com <none>                          (no description available)
pn  ucf      <none>                          (no description available)
ii  zlib1g   1:1.2.3-13                      compression library - runtime

libapache2-mod-php4 recommends no packages.

-- no debconf information



Information forwarded to [email protected], Debian PHP Maintainers <[email protected]>:
Bug#399215; Package libapache2-mod-php4. (full text, mbox, link).


Acknowledgement sent to Steve Langasek <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian PHP Maintainers <[email protected]>. (full text, mbox, link).


Message #10 received at [email protected] (full text, mbox, reply):

From: Steve Langasek <[email protected]>
To: Jari Aalto <[email protected]>, [email protected]
Subject: Re: Bug#399215: libapache2-mod-php4: Emacs readline problem "What would you like to do about php.ini?"
Date: Sat, 18 Nov 2006 15:03:57 -0800
reassign 399215 ucf
thanks

On Sat, Nov 18, 2006 at 06:08:30PM +0200, Jari Aalto wrote:
> While upgrading under Emacs terminal (M-x shell) it reads:

>     Setting up php4-common (4.4.4-7) ...
>     Setting up libapache2-mod-php4 (4.4.4-7) ...
>     debconf: unable to initialize frontend: Dialog
>     debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
>     debconf: falling back to frontend: Readline
>     What would you like to do about php.ini? 

> SUGGESTION

> - The question presented is not clear. Please print an introductory message explaining
>   what is the problem, why the question are asked and what are the choices to the question.
> - Please always state all path names in full, like php.ini in this case.

This question comes from ucf; reassigning.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[email protected]                                   http://www.debian.org/



Bug reassigned from package `libapache2-mod-php4' to `ucf'. Request was from Steve Langasek <[email protected]> to [email protected]. (full text, mbox, link).


Information forwarded to [email protected], Manoj Srivastava <[email protected]>:
Bug#399215; Package ucf. (full text, mbox, link).


Acknowledgement sent to Jari Aalto <[email protected]>:
Extra info received and forwarded to list. Copy sent to Manoj Srivastava <[email protected]>. (full text, mbox, link).


Message #17 received at [email protected] (full text, mbox, reply):

From: Jari Aalto <[email protected]>
To: Steve Langasek <[email protected]>
Cc: [email protected]
Subject: Re: Bug#399215: libapache2-mod-php4: Emacs readline problem "What would you like to do about php.ini?"
Date: 19 Nov 2006 01:30:56 +0200
Steve Langasek <[email protected]> writes:

> reassign 399215 ucf
> thanks
> 
> On Sat, Nov 18, 2006 at 06:08:30PM +0200, Jari Aalto wrote:
> > While upgrading under Emacs terminal (M-x shell) it reads:
> 
> >     Setting up php4-common (4.4.4-7) ...
> >     Setting up libapache2-mod-php4 (4.4.4-7) ...
> >     debconf: unable to initialize frontend: Dialog
> >     debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
> >     debconf: falling back to frontend: Readline
> >     What would you like to do about php.ini? 
> 
> > SUGGESTION
> 
> > - The question presented is not clear. Please print an introductory message explaining
> >   what is the problem, why the question are asked and what are the choices to the question.
> > - Please always state all path names in full, like php.ini in this case.
> 
> This question comes from ucf; reassigning.

Additional detail:

There are choices displayed, but only *after* user presses return to the prompt

   What would you like to do about php.ini? 

Somehow the messages come in wrong order. The 1) 2) 3) ... choices
should appear first and then the question "php.ini?". However, this
isn't happening in Emacs M-x shell.

Jari




Information forwarded to [email protected], Manoj Srivastava <[email protected]>:
Bug#399215; Package ucf. (full text, mbox, link).


Acknowledgement sent to Manoj Srivastava <[email protected]>:
Extra info received and forwarded to list. Copy sent to Manoj Srivastava <[email protected]>. (full text, mbox, link).


Message #22 received at [email protected] (full text, mbox, reply):

From: Manoj Srivastava <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: Bug#399215: libapache2-mod-php4: Emacs readline problem "What would you like to do about php.ini?"
Date: Sat, 18 Nov 2006 21:52:03 -0600
reassign 399215 debconf
thanks

Hi,

        So in emacs shell, or for a dumb terminal  the choices for a
 multi choice select question are presented _after_ the question is.

        manoj
-- 
What's so funny?
Manoj Srivastava <[email protected]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



Bug reassigned from package `ucf' to `debconf'. Request was from Manoj Srivastava <[email protected]> to [email protected]. (full text, mbox, link).


Information forwarded to [email protected], Debconf Developers <[email protected]>:
Bug#399215; Package debconf. (full text, mbox, link).


Acknowledgement sent to Joey Hess <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debconf Developers <[email protected]>. (full text, mbox, link).


Message #29 received at [email protected] (full text, mbox, reply):

From: Joey Hess <[email protected]>
To: [email protected]
Cc: Jari Aalto <[email protected]>
Subject: probably a misfeature in emacs's shell
Date: Wed, 10 Jan 2007 00:52:23 -0500
[Message part 1 (text/plain, inline)]
In the readline frontend, debconf always displays choices first, and
only then prompts for input. If emacs choses to for some reason display
the prompt first, that seems like it would be a bug in emacs.

It's a bit difficult to know for sure, since you don't provide any details
about what version of emacs you're using, what perl readline modules you have
installed, etc. Also, I can't really fathom why you'd want to use the readline
frontend inside emacs; the teletype frontend seems better suited to it.

-- 
see shy jo
[signature.asc (application/pgp-signature, inline)]

Information forwarded to [email protected], Debconf Developers <[email protected]>:
Bug#399215; Package debconf. (full text, mbox, link).


Acknowledgement sent to Jari Aalto <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debconf Developers <[email protected]>. (full text, mbox, link).


Message #34 received at [email protected] (full text, mbox, reply):

From: Jari Aalto <[email protected]>
To: Joey Hess <[email protected]>
Cc: [email protected]
Subject: Re: probably a misfeature in emacs's shell
Date: Wed, 10 Jan 2007 16:55:25 +0200
Joey Hess <[email protected]> writes:

> In the readline frontend, debconf always displays choices first, and
> only then prompts for input. If emacs choses to for some reason display
> the prompt first, that seems like it would be a bug in emacs.
>
> It's a bit difficult to know for sure, since you don't provide any details
> about what version of emacs you're using, what perl readline modules you have
> installed, etc. 

ii  emacs-goodies-el  26.9-1            Miscellaneous add-ons for Emacs
ii  emacs21           21.4a+1-3         The GNU Emacs editor
ii  emacs21-bin-commo 21.4a+1-3         The GNU Emacs editor's shared, architecture depend
ii  emacs21-common    21.4a+1-3         The GNU Emacs editor's shared, architecture indepe
ii  emacs21-el        21.4a+1-3         GNU Emacs LISP (.el) files
ii  emacsen-common    1.4.17            Common facilities for all emacsen
ic  libreadline4      4.3-18            GNU readline and history libraries, run-time libra
ii  libreadline5      5.2-2             GNU readline and history libraries, run-time libra
ii  libreadline5-dev  5.2-2             GNU readline and history libraries, development fi
ii  libterm-readline- 1.16-2            Perl extension for the GNU Readline/History Librar
ii  readline-common   5.2-2             GNU readline and history libraries, common files

> Also, I can't really fathom why you'd want to use the readline
> frontend inside emacs; the teletype frontend seems better suited to it.

copy/cut/paste and moving pieces and commands arund with macros etc.
It's quite obvious environment.

Jari





Send a report that this bug log contains spam.


Debian bug tracking system administrator <[email protected]>. Last modified: Thu Nov 14 10:29:40 2024; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.