chris dunder ccdunder

## emacs-24.4-24bit.diff
This diff is a modified version of a diff written by Rüdiger Sonderfeld.

The original diff can be found here:

http://emacs.1067599.n5.nabble.com/RFC-Add-tty-True-Color-support-tt299962.html

To enable the feature one must set one of 2 environment variables either
ITERM_24BIT or KONSOLE_DBUS_SESSION. The former will enable ITU T.416 mode, the
latter will use semi-colon seperators used by other terminals (and also
supported by iterm development branch).

## TrueColour.md

      
              1 file
            
          
              168 forks
            
          
              328 comments
            
          
              2354 stars
            
          
                XVilka
                / TrueColour.md
            
            
              Last active
              April 8, 2024 14:02
            
              
                True Colour (16 million colours) support in various terminal applications and terminals
              
          
    THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

  
## gist:710671
So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

* Off the top of my head *

1. Fork their repo on Github
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork git@github...my-fork.git
	This diff is a modified version of a diff written by Rüdiger Sonderfeld.

	The original diff can be found here:

	http://emacs.1067599.n5.nabble.com/RFC-Add-tty-True-Color-support-tt299962.html

	To enable the feature one must set one of 2 environment variables either
	ITERM_24BIT or KONSOLE_DBUS_SESSION. The former will enable ITU T.416 mode, the
	latter will use semi-colon seperators used by other terminals (and also
	supported by iterm development branch).
	So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

	Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

	* Off the top of my head *

	1. Fork their repo on Github
	2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

	git remote add my-fork git@github...my-fork.git