bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#5067: marked as done (23.1.50; Why doesn't eshell/pcomplete use ~ an


From: Emacs bug Tracking System
Subject: bug#5067: marked as done (23.1.50; Why doesn't eshell/pcomplete use ~ any more?)
Date: Sat, 28 Nov 2009 17:15:05 +0000

Your message dated Sat, 28 Nov 2009 12:09:35 -0500
with message-id <address@hidden>
and subject line Re: bug#5067: 23.1.50; Why doesn't eshell/pcomplete use ~ any 
more?
has caused the Emacs bug report #5067,
regarding 23.1.50; Why doesn't eshell/pcomplete use ~ any more?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
5067: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=5067
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.1.50; Why doesn't eshell/pcomplete use ~ any more? Date: Sat, 28 Nov 2009 14:07:28 +0000
I just upgraded my Emacs.app to CVS 20091127 and eshell seems to behave
abnormally as compared to my previous version (CVS 20090922).

For example, if I 'cd ~', the prompt will be the absolute path of my
HOME dir instead of just '~' like in the previous version.

With (setq eshell-cmpl-ignore-case t), 'cd ~/l<TAB>' throws this error:

  pcomplete-insert-entry: Text is read-only
  pcomplete: Wrong type argument: integerp, nil [8 times]

Could someone take a look at this bug? Thank you.

Leo

--------------------------------

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
For information about debugging Emacs, please read the file
/Applications/Emacs.app/Contents/Resources/etc/DEBUG.


In GNU Emacs 23.1.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
 of 2009-11-27 on victoria.local
Windowing system distributor `Apple', version 10.3.949
configured using `configure  '--with-ns''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  value of $XMODIFIERS: nil
  locale-coding-system: nil
  default enable-multibyte-characters: t

Major mode: LaTeX/FMP

Minor modes in effect:
  diff-auto-refine-mode: t
  shell-dirtrack-mode: t
  reftex-mode: t
  TeX-fold-mode: t
  LaTeX-math-mode: t
  TeX-PDF-mode: t
  dired-omit-mode: t
  recentf-mode: t
  icomplete-mode: t
  ido-everywhere: t
  savehist-mode: t
  display-time-mode: t
  xterm-mouse-mode: t
  delete-selection-mode: t
  global-auto-revert-mode: t
  minibuffer-depth-indicate-mode: t
  show-paren-mode: t
  rcirc-track-minor-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  visual-line-mode: t
  transient-mark-mode: t


--- End Message ---
--- Begin Message --- Subject: Re: bug#5067: 23.1.50; Why doesn't eshell/pcomplete use ~ any more? Date: Sat, 28 Nov 2009 12:09:35 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
> For example, if I 'cd ~', the prompt will be the absolute path of my
> HOME dir instead of just '~' like in the previous version.

I installed a change which should fix it (unless you've customized
eshell-prompt-function, in which case you'll have to make the change in
your cutomization).

> With (setq eshell-cmpl-ignore-case t), 'cd ~/l<TAB>' throws this error:

>   pcomplete-insert-entry: Text is read-only
>   pcomplete: Wrong type argument: integerp, nil [8 times]

> Could someone take a look at this bug? Thank you.

Thanks for catching this.  It was some half-cooked change I have here
that I installed mistakenly as part of some other change.  I reverted it
now, so it should work as before.


        Stefan

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]