Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 235928 - xemacs tabify/untabify not working
xemacs tabify/untabify not working
Product: Fedora
Classification: Fedora
Component: xemacs (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-04-10 16:40 EDT by Tim Taiwanese Liim
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-11 11:07:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Taiwanese Liim 2007-04-10 16:40:43 EDT
Description of problem:
    The tabify/untabify command disappears in FC6.  It was available 
    in FC5 (xemacs 21.4 (patch 19)).

Version-Release number of selected component (if applicable):
    XEmacs 21.5  (beta27) "fiddleheads" (linux, Mule) of Thu Jan 25 2007 on hammer2
    [version 21.5.27 of May 2006]

How reproducible:

Steps to Reproduce:
    1. start xemacs
    2. M-x tabify
Actual results:
    - tabify unrecognized.  Same for untabify.

Expected results:
    - command tabify should be available.

Additional info:
Comment 1 Tim Taiwanese Liim 2007-04-10 22:53:42 EDT
Some other commands that are missing since FC5:
Maybe they are missing for a good reason that I don't understand.
Comment 2 Jens Petersen 2007-04-10 23:20:50 EDT
I suspect you're missing some xemacs-sumo packages since they're not
all installed by default any more.
Comment 3 Ville Skyttä 2007-04-11 11:07:08 EDT
Right, install the xemacs-packages-extra package.  It's regrettable that during
the FC5->FC6 upgrade, xemacs-packages-extra was not pulled in for people who had
xemacs-sumo installed.
Comment 4 Tim Taiwanese Liim 2007-04-11 11:28:54 EDT
Thanks!  Yes xemacs-packages-extra solved the issue.  Yes it's
rather hard for users to guess which xemacs-related rpms to pull in.

Note You need to log in before you can comment on or make changes to this bug.