rofi -width setting ignored. about buku_run HOT 6 CLOSED

See line 3 of the script. This can be overridden in the config file. Just copy the buku.config file to $HOME/.config/buku_run/config and edit the options in the _rofi function on top.

from buku_run.

Thanks for getting back. I already edited the -width option in $HOME/.config/buku_run/config. Did not have any effect. Hmmmm. I ended up finding a workaround, though I do not no if its an appropriate or clean way to accomplish it, works though. I edited line 44 in the script:

content=$(buku -p -f 2 | awk 'NF == 2 { $0 = $0 "NOTAG" }; { $2 = substr($2,0,170); print 
$1"\t"$2"\t"$3,$4,$5 }' | column -t -s $'\t') 

I changed:

{ $2 = substr($2,0,60); 

to

{ $2 = substr($2,0,170); 

If I am honest i dont know why it worked, but it did the job....

from buku_run.

That's more than strange, I just tried and setting width in config file works just fine... Since you are using fullscreen, just get rid of the -width parameter completely.

from buku_run.

Hmmm. Strange indeed.

Okay. I removed the -width parameter completely, has no effect. If you want, here is a link of a few images to clarify what I am talking about. I am not positive we are on the same page regarding how I was expecting the bookmarks to display. Buku_run might be working as expected.

Both images have the -width parameter removed. One has my "workaround" in it. The third is a rofi search script I use, just as an example of how my other rofi scripts display at fullscreen. As far as I am concerned, all is good after my edit.

And just a note, I normally wouldnt post a pic of my bookmarks online or would at least blur them, but the link will expire and im not worried about you and maybe a few other people seeing them for troubleshooting purposes.

Edit: Link removed.

from buku_run.

Ah, indeed I was thinking something else. I don't think this can be solved in an elegant way. One could make the width for urls configurable in config I guess.

from buku_run.

Okay, thats cleared up then. I did not want you thinking your script was broken in some random way, and i was not sure if something funky might be going on with my set up.

I suppose it depends on what size the user is using rofi. If one is using rofi at the default size, the width of the urls make total sense. I am assuming I am the only one that brought this up at this point, so Its prob a non-issue for 99% of users.

lastly, In hindsight I realize I should have had clarified I have rofi -padding set to 0. My bad. Ill close this non "issue" now.

from buku_run.