Luc Teirlinck <[EMAIL PROTECTED]> writes:
> I do not get these errors, because my loaddefs.el is up to date.
>
>the desired behavior is ability to load/use info, dired, rmail, without
>having to load desktop.el. if i don't use desktop.el, i don't want it
>loaded (or autoloaded), *eve
Thien-Thi Nguyen wrote:
dired.el, info.el, (and i just noticed) mail/rmail.el fail to load
because the variable `desktop-buffer-mode-handlers' is not defined.
the scenario occurs when one doesn't load desktop.el ever.
`desktop-buffer-mode-handlers' is defined, even if d
the desired behavior is ability to load/use info, dired, rmail, without
having to load desktop.el.
After doing `C-x d', `C-h i' and `M-x rm' without any problems and
_without having your recent changes installed_, I get:
ELISP> desktop-buffer-mode-handlers
((Info-mode . Info-restore-desktop
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> Can you tell how to reproduce the bugs these changes are supposed to fix:
dired.el, info.el, (and i just noticed) mail/rmail.el fail to load
because the variable `desktop-buffer-mode-handlers' is not defined.
the scenario occurs when on
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> I am suspicious about this because somebody else reported bugs
> concerning `desktop-buffer-mode-handlers', info and dired that
> definitely were only due to failure to update loaddefs.el.
>
> Assuming the bugs your changes are supposed to fix are real
Can you tell how to reproduce the bugs these changes are supposed to fix:
2005-08-14 Thien-Thi Nguyen <[EMAIL PROTECTED]>
* dired.el: Fix dependency bug: Wrap `desktop-buffer-mode-handlers'
modification in `eval-after-load' form.
* info.e
One more remark on the following change:
2005-08-14 Thien-Thi Nguyen <[EMAIL PROTECTED]>
* dired.el: Fix dependency bug: Wrap `desktop-buffer-mode-handlers'
modification in `eval-after-load' form.
* info.el: Likewise.
I am suspicious ab
The change is in the sorting order (it was in reverse order before
this change) and minor formatting details.
Ok, I don't object to that.
But since `S' binding doesn't hurt, let's leave it alone, and remove
only its menu item from the Info menu. Currently this menu is too big
>isearch has the command to toggle the case sensitivity - `M-c',
>and it is possible to use it to search the whole Info manual.
>
>But since `S' binding doesn't hurt, let's leave it alone, and remove
>only its menu item from the Info menu. Currently this menu is too big
>alread
Juri Linkov wrote:
isearch has the command to toggle the case sensitivity - `M-c',
and it is possible to use it to search the whole Info manual.
But since `S' binding doesn't hurt, let's leave it alone, and remove
only its menu item from the Info menu. Currently this menu is too big
Juri Linkov wrote:
But since `S' binding doesn't hurt, let's leave it alone, and remove
only its menu item from the Info menu. Currently this menu is too big
already, and it would be good to retain only basic commands in it.
Sorry, I may have misunderstood you. I thought that you were
> 5. Fixed `info-apropos' to work exactly as `index-apropos' in the
>stand-alone Info reader.
>
> Could you say more specifically what the change is?
The change is in the sorting order (it was in reverse order before
this change) and minor formatting details.
> 7. Removed `S' bind
5. Fixed `info-apropos' to work exactly as `index-apropos' in the
stand-alone Info reader.
Could you say more specifically what the change is?
7. Removed `S' binding (`Info-search-case-sensitively') since it is not
useful anymore with isearch working on the whole Info manual
While updating info.texi, I took the opportunity to fix info.el:
1. Replaced `info' with upper-case `Info' where appropriate.
2. Renamed `info-menu-5' face to `info-menu-star'.
3. Grouped face definitions together.
4. Put the cursor on menu items in the same way as on cros
14 matches
Mail list logo
