dbordak / telephone-line

A new implementation of Powerline for Emacs
GNU General Public License v3.0
550 stars 51 forks source link

Text scale in segments #79

Open ogdenwebb opened 6 years ago

ogdenwebb commented 6 years ago

Is there built-in ability to scale text within telephone-line? Would you add something similar to powerline-text-scale-factor? Probably this related to a generic padding keyword in #40.

dbordak commented 6 years ago

If you're talking about the whole bar, why not just change the font size? The separator height changes automatically (although you might have to clear the cache).

Per-segment is kinda dicey and I don't think it'd work.

ogdenwebb commented 6 years ago

If you're talking about the whole bar, why not just change the font size?

Yes, generally I ask about change the font size whole mode-line. I've tried, but my mode-line doesn't fit well. As you can see, I got some extra space aftrer mode-line.

2018-08-20-140446_962x69_scrot

I tried this.

(set-face-attribute 'mode-line nil :font "DejaVu Sans Mono-10")

Even if I set :height 100 for example in face definition, my mode-line still looks like the above.

although you might have to clear the cache

How can I achieve that?

dbordak commented 6 years ago

Sorry, this isn't what I thought it was at first -- this is just a bug. I'll look into it next week, don't have any time for it right now.

dbordak commented 6 years ago

Alright, just in case, here's how you clear the caches:

(telephone-line-separator-clear-cache telephone-line-cubed-left)
(telephone-line-separator-clear-cache telephone-line-cubed-right)

...and two more for your subseparators, if you're using them (can't really see from the screenshot?).

I should probably add a function for doing this...

ogdenwebb commented 6 years ago

can't really see from the screenshot?

No, I don't use them.

Alright, just in case, here's how you clear the caches

It doesn't help though, the same result as above.

sebasmonia commented 4 years ago

@ogdenwebb it's likely that the (partial) merge in PR #104 will help with this issue, FYI.