[BUG] Failure to propagate formatting overrides via ConsoleOptions

[kmvanbrunt]

• I've checked docs and closed issues for possible solutions.
• I can't find my issue in the FAQ.

⚠️ UPDATE: Revised Scope
Upon further investigation, this is not limited to a missing emoji setting.

There are two core issues

1. ConsoleOptions is missing an emoji field. Therefore, emoji overrides passed to console.print() are ignored.
2. Multiple classes (Table, Rule, Columns, and Measure) fail to pass some or all of emoji, markup, and highlight settings from their ConsoleOptions back to console.render_str().

I have a fix but I am currently unable to create a pull request in this repo.

See this fork for the fix:
https://github.com/kmvanbrunt/rich/tree/emoji_console_option

Original Description

When printing a complex renderable like a Table, passing emoji=False to console.print() does not disable emoji parsing within the table cells if the Console was initialized with emoji=True (the default).

This appears to be because ConsoleOptions does not include an emoji field, and Console.render() does not propagate the emoji preference to render_str().

Here is code to reproduce the bug.

from rich.console import Console
from rich.table import Table

# Create Console with markup and emoji enabled
console = Console(markup=True, emoji=True)
t = Table(show_header=False)
t.add_row("[blue]some text[/blue]", ":1234:")

print("Normal print() shows markup and emoji rendering")
console.print(t)

# Attempt to override markup and emoji when printing a Table
print("Print overrides only work for markup and the emoji still renders")
console.print(t, markup=False, emoji=False)

Here is a screenshot of the results.

Platform
rich==14.3.3
Python 3.11.2
Debian 12.13

[github-actions]

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

Rich was created by Will McGugan. Consider sponsoring Will's work on Rich.

This is an automated reply, generated by FAQtory

[kmvanbrunt]

I created a fix for this at: https://github.com/kmvanbrunt/rich/tree/emoji_console_option
I will submit a pull request for it soon.

It fixes two issues.

1. Added the emoji field to ConsoleOptions, allowing emoji overrides passed to console.print() to be propagated down the rendering stack.

2. Fixed several instances (Table, Rule, Columns, and Measure) where the renderables were calling console.render_str() but failing to pass the some or all of emoji, markup, and highlight settings from the active ConsoleOptions.

[mariettakyriazi]

Hi! I can reproduce this on Windows (Python 3.11). I’d like to work on a PR with a regression test.

I saw you mentioned having a fix in your fork/branch. If you’re about to open a PR, I’m happy to help by adding tests / reviewing. Otherwise I’ll proceed with my own PR shortly.

[kmvanbrunt]

@mariettakyriazi Rich is currently restricting who can submit pull requests. I am seeing this message when I try.

An owner of this repository has limited the ability to open a pull request to users that are collaborators on this repository.

I have previously submitted Rich PRs so I'm not sure why it's locked down right now.

My fork has a complete fix, but I've not written tests yet.
https://github.com/kmvanbrunt/rich/tree/emoji_console_option

If you're able to submit a PR to Rich and you feel my solution is complete, feel free to submit what I have.

[mariettakyriazi]

Hi! I implemented a fix + regression test for this.

Fork PR (for reference): mariettakyriazi#1

GitHub currently blocks me from opening a PR directly to Textualize/rich (PRs restricted to collaborators). If helpful, a maintainer can cherry-pick my commit or I can provide a patch file.

Credits: thanks to @kmvanbrunt for the analysis in #4028.

[mariettakyriazi]

Cherry-pick (fix + formatting):
git fetch https://github.com/mariettakyriazi/rich.git fix-4028-emoji-options
git cherry-pick cc867a2 48e41b1 46fac29

[kmvanbrunt]

@mariettakyriazi I appreciate your effort, but your changes do not address the entire issue. My fork already has a complete fix, so you don't need to submit one. I will create the pull request once Rich removes the restrictions.