Menu ▾ ▴

#387 Custom command line does not take full path

1.0.1
closed-fixed
Lonely Stranger
libfm (316)
5
2014-10-20
2010-11-11
Anonymous
No

When using the custom command line option in the open-with dialog, full path names are not accepted:

foo %f -> file is opened

/usr/bin/foo %f -> nothing happens, debug says "bin1 = /usr/bin/foo"

Discussion

  • PCMan

    PCMan - 2011-11-18

    Version 1.0 is in feature freeze and string freeze now.
    Let's fix this later in 1.5.

     

  • PCMan

    PCMan - 2011-11-18

    this may requires some changes in the UI.
    Let's do it later.

     

  • PCMan

    PCMan - 2011-11-18
    • milestone: --> 2297538
    • status: open --> open-later
     

  • Lonely Stranger

    Lonely Stranger - 2012-07-16
    • milestone: 2297538 --> 2334032
     

  • Lonely Stranger

    Lonely Stranger - 2012-07-18
    • labels: --> libfm
     

  • Lonely Stranger

    Lonely Stranger - 2012-08-10
    • milestone: 2334032 --> 1.0.1
    • assigned_to: nobody --> lstranger
    • status: open-later --> open-accepted
     

  • Lonely Stranger

    Lonely Stranger - 2012-08-13
    • status: open-accepted --> closed-fixed
     

  • Lonely Stranger

    Lonely Stranger - 2012-08-13

    We hope this issue is completely fixed in the Git repository recently.
    Check it out when it's possible for you and if the bug still exists then reopen the report, please.
    Thank you very much.

     

Anonymous
Anonymous

Add attachments
Cancel