Enable Firefox support for atomic-chrome browser integration#1
Closed
narendraj9 with Copilot wants to merge 1 commit into
Closed
Enable Firefox support for atomic-chrome browser integration#1narendraj9 with Copilot wants to merge 1 commit into
narendraj9 with Copilot wants to merge 1 commit into
Conversation
Copilot
AI
changed the title
[WIP] Make this chrome plugin work on firefox in addition to chrome.
Enable Firefox support for atomic-chrome browser integration
Sep 18, 2025
Copilot stopped work on behalf of
narendraj9 due to an error
September 18, 2025 23:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the atomic-chrome configuration to work with both Chrome and Firefox browsers. The previous configuration was incomplete - it only set up hooks but didn't start the websocket server that browser extensions connect to.
Problem
The existing atomic-chrome configuration in
init.elwas missing the crucial(atomic-chrome-start-server)call, which meant browser extensions couldn't connect to Emacs for text area editing functionality.Solution
(atomic-chrome-start-server)in the:configsection to start the websocket serverChanges Made
Usage
After this change, users can:
C-c C-cto finish editingThe same configuration now works seamlessly with both browsers through the unified GhostText extension.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
melpa.orgcurl -s REDACTED(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.