Bug 1442628 - Fish autocompletion for "lua -l" is broken
Summary: Fish autocompletion for "lua -l" is broken
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fish
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andy Lutomirski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-16 19:23 UTC by Hugo
Modified: 2017-12-12 10:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:17:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hugo 2017-04-16 19:23:43 UTC
Description of problem:

The autocomplete script for Lua in the Fish shell is broken when using Lua's "-l" flag.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------

I am using Fedora 25. The versions installed on my machine are fish 2.3.1 and Lua 5.3.4


How reproducible:
-----------------

Every time

Steps to Reproduce:
-------------------

1. Install both the "fish" and "lua" packages.
2. In the fish prompt, type "lua -l".
3. Press the Tab key.

Actual results:
---------------

It errors out with a "find: ‘/usr/lib/lua/’: No such file or directory" error message.

Expected results:
-----------------

It should suggest a list of available module names you can put after "-l"

Additional info:
---------------

Apparently this is because in Fedora the Lua libraries are located on /usr/lib64/lua instead of /usr/lib/lua. I worked around this on my machine by editing /usr/share/fish/completions/lua.fish to use "lib64" instead of "lib" but  I'm not sure if this is the proper way to fix the issue.

I also checked on the upstream git repository[1] and their version of the completions/lua.fish file is the same as the one that is currently installed on my machine. So my issue would persist even if we updated fish to the latest version.

[1] https://github.com/fish-shell/fish-shell/blob/master/share/completions/lua.fish

Comment 1 Fabian Homborg 2017-04-20 12:06:23 UTC
Hello, it's your friendly neighborhood fish developer!

This has been fixed upstream in https://github.com/fish-shell/fish-shell/commit/cb9f4e621fcaf83ba292292a9815d216715f2934 and will be included in the 2.6.0 release.

The beta has been planned for 23-04-17, so the release is expected in the beginning of may.

Comment 2 Fedora End Of Life 2017-11-16 18:39:08 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:17:22 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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