-
-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Description
brew gist-logs <formula>
link OR brew config
AND brew doctor
output
> brew config
HOMEBREW_VERSION: 4.5.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: 6f39076b3c2251994419215279d0525ef667fc31
Last commit: 12 days ago
Branch: stable
Core tap JSON: 21 May 11:51 UTC
Core cask tap JSON: 21 May 11:51 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.RCguznumGW/org.xquartz:0
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.4.3 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.4.3/bin/ruby
CPU: deca-core 64-bit arm_firestorm_icestorm
Clang: 17.0.0 build 1700
Git: 2.49.0 => /opt/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.5-arm64
CLT: 16.3.0.0.1.1742442376
Xcode: 16.3
Rosetta 2: false
> brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
icu4c@76
Warning: The following formulae have the same name as core formulae:
hashicorp/tap/consul-template
hashicorp/tap/levant
hashicorp/tap/nomad
hashicorp/tap/packer
hashicorp/tap/terraform
hashicorp/tap/terraform-ls
hashicorp/tap/vault
hashicorp/tap/waypoint
Their taps are in use, so you must use these full names throughout Homebrew.
Warning: Putting non-prefixed findutils in your path can cause python builds to fail.
Verification
- My
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue. - I ran
brew update
and am still able to reproduce my issue. - I have resolved all warnings from
brew doctor
and that did not fix my problem. - I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.
What were you trying to do (and why)?
I was trying to run xterm -fa "Codelia" -fb "Codelia Bold" -fs 10 -bg black -fg grey -sb -sl 100000 -rightbar -tn xterm-256color &
and xterm complained that the -fa
is bad. Removing that, I tried again, and it complained that the -fs
parameter was bad. Both of these options work in xterm 398 from homebrew. I am unable to test xterm 399 from outside of homebrew as I am unable to compile it from source. The xterm changelog does not mention this change.
What happened (include all command output)?
> xterm -fa "Codelia" -fb "Codelia Bold" -fs 10 -bg black -fg grey -sb -sl 100000 -rightbar -tn xterm-256color &
xterm: bad command line option "-fa"
usage: xterm [-/+132] [-C] [-Sccn] [-T string] [-/+ah] [-/+ai] [-/+aw]
[-b number] [-baudrate rate] [-/+bc] [-bcf milliseconds]
[-bcn milliseconds] [-bd color] [-/+bdc] [-bg color] [-bw number] [-/+cb]
[-cc classrange] [-/+cjk_width] [-class string] [-/+cm] [-/+cn] [-cr color]
[-/+cu] [-/+dc] [-display displayname] [-e command args ...] [-fb fontname]
[-/+fbb] [-/+fbx] [-fc fontmenu] [-fg color] [-fi fontname] [-fn fontname]
[-/+fullscreen] [-fw fontname] [-fwb fontname] [-fx fontname] [#geom]
[%geom] [-geometry geom] [-help] [-/+hm] [-/+hold] [-iconic] [-/+ie]
[-/+im] [-into windowId] [-/+itc] [-/+j] [-/+k8] [-kt keyboardtype] [-/+l]
[-/+lc] [-lcc path] [-leftbar] [-lf filename] [-/+ls] [-/+maximized]
[-/+mb] [-mc milliseconds] [-/+mesg] [-/+mk_width] [-ms color] [-n string]
[-name string] [-nb number] [-/+nomap] [-/+nul] [-/+pc] [-pf fontname]
[-/+pob] [-report-charclass] [-report-colors] [-report-fonts]
[-report-icons] [-report-xres] [-rightbar] [-/+rv] [-/+rvc] [-/+rw] [-/+s]
[-/+samename] [-/+sb] [-selbg color] [-selfg color] [-/+sf] [-sh number]
[-/+si] [-/+sk] [-sl number] [-/+sm] [-/+sp] [-/+t] [-ti termid]
[-title string] [-tm string] [-tn name] [-/+u8] [-/+uc] [-/+ulc] [-/+ulit]
[-/+ut] [-/+vb] [-version] [-/+wc] [-/+wf] [-xrm resourcestring]
[-ziconbeep percent]
Type xterm -help for a full description.
fish: Job 1, 'xterm -fa "Codelia" -fb "Codeli…' has ended
> xterm -v
XTerm(399)
What did you expect to happen?
I expect the -fa
and -fs
options to work. they worked in xterm 398. unfortunately I don't know if this is a regression in the homebrew formula (seems doubtful, the change to 399 here doesn't change how xterm is built from what I can see) or if this is a regression in xterm itself (this also seems extremely unlikely.)
Step-by-step reproduction instructions (by running brew
commands)
brew update
brew upgrade
xterm -fa "Codelia" -fb "Codelia Bold" -fs 10 -bg black -fg grey -sb -sl 100000 -rightbar -tn xterm-256color
I imagine any opentype or truetype font would work in exchange for Codelia.