bugranger - Bugs: bug #39762, scope.sh should use printf instead...


bug #39762: scope.sh should use printf instead of echo

Submitter:  None
Submitted:  Sun 11 Aug 2013 05:03:00 PM UTC
Severity:  3 - Normal Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Fri 01 Nov 2013 10:19:51 PM UTC, comment #1: 

I can't reproduce this. I made a file containing newlines and a file containing a literal "\n", both didn't produce any effect out of the ordinary.

Roman Z. <hut>
Group administrator
Sun 11 Aug 2013 05:03:00 PM UTC, original submission:  

If there is "\n" in some text file, it breaks ranger's preview with highlighting. It can be fixed by changing line:
    dump() { echo "$output"; }
    dump() { printf '%s\n' "$output"; }



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by hut (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-11-01 hut StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code