这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Finii
Copy link
Collaborator

@Finii Finii commented Nov 30, 2021

Description

[why]
When the font file is not existing the message we get is either
unreadable or misleading (at least for normal users).

[how]
Explicitly state why we can not open a font file, at least in the cases
where we can.

Requirements / Checklist

  • Read the Contributing Guidelines
  • Read or at least glanced at the FAQ
  • Read or at least glanced at the Wiki
  • Scripts execute without error (if necessary):
    • If any of the scripts were modified they have been tested and execute without error, e.g.:
      • ./font-patcher Inconsolata.otf --fontawesome --octicons --pomicons
      • ./gotta-patch-em-all-font-patcher\!.sh Hermit
  • Extended the README and documentation if necessary, e.g. You added a new font please update the table

What does this Pull Request (PR) do?

Improve error messages on font open fail.

How should this be manually tested?

Try to patch a non-existing font file. Try to patch a write-only file.

Any background context you can provide?

What are the relevant tickets (if any)?

#512 (comment)

Screenshots (if appropriate or helpful)

With this MR:

image

[why]
When the font file is not existing the message we get is either
unreadable or missleading (at least for normal users).

[how]
Explicitely state why we can not open a font file, at least in the cases
where we can.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
@ryanoasis ryanoasis merged commit bbe2543 into master Dec 5, 2021
@ryanoasis ryanoasis deleted the feature/enhance-open-error-msg branch December 5, 2021 00:13
LNKLEO pushed a commit to LNKLEO/Nerd that referenced this pull request Nov 24, 2023
…error-msg

font-patcher: Give meaningful error messages on trivial open fails
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants