extension ExtPose

gTalk Syntax Highlighting

CRX id

okpdnaeoefggpaccmolhoaiffmmdoool-

Description from extension meta

Automatic Syntax Highlighting for gChat.

Image from store gTalk Syntax Highlighting
Description from store This plugin automatically detects when you type code whilst conversing with google talk, and adds syntax highlighting to it. - Allows inline code blocks with `backticks` - Detects code presence, and correct way to highlight said code. - Has a manual control, for cases where the auto-detection fails. - Optionally attach your own machine-learning server. - Project page on github: https://github.com/pehrlich/GTalkSyntax Important: You must reload your GMail tab after first installing this plugin. Once you do, any chat will auto-highlight code! CHANGES: 0.3.0 (accessories release) - Copy to clipboard, link to this plugin, in a lightly styled menu - Now supports gTalk with "Pictures in chat" labs extension turned off - Donate button, toggle switch, and fork banner on options page - Google analytics for click events - Sexy new icon.

Latest reviews

  • (2019-01-11) metal cobaleda: tsh
  • (2013-12-20) Michael Grove: does not work
  • (2013-10-16) Chad Slappey: Don't think it works with new Google Hangouts
  • (2013-04-10) Denis Feoktistov: Pls allow to user change font size =(
  • (2013-02-19) Bill Broadley: way way way too many false positives.
  • (2013-02-08) Pyarelal Knowles: Think it needs some more work. More sentences were highlighted automatically than code. The "text/code" mouseover didn't appear for some blocks. Highlighting seems to be a grey background, not colour (C/C++/python tested).
  • (2013-01-29) Patrick Stapleton: not bad *Obama face*

Latest issues

  • (2013-05-01, v:0.3.4) Ben K: Android Logcat Highlighter?
    Hi, I do a lot of debugging for android, and it would be great to get a highlighter for viewing these logcat files. Here is a sample of a pastebin file: http://pastebin.com/yfupSbKw A logcat will always begin with the string "--------- beginning of /dev/log/system" Also, here is a sample of code from a .vim file that does simple highlighting: hi def LogF_color ctermfg=white guifg=white ctermbg=red guibg=red hi def LogE_color ctermfg=red guifg=red hi def LogW_color ctermfg=brown guifg=brown hi def LogI_color ctermfg=blue guifg=blue hi def LogD_color ctermfg=darkgreen guifg=darkgreen hi def LogV_color ctermfg=gray guifg=gray syn match LogF 'F/.*' syn match LogE 'E/.*' syn match LogW 'W/.*' syn match LogI 'I/.*' syn match LogD 'D/.*' syn match LogV 'V/.*' The various error levels are the denoted by F/, E/, W/, etc. So, an example line: "E/Trace ( 1004): error opening trace file: No such file or directory (2)" I would picture as formatted so that E/Trace ( 1004): would have a colored value specific to the debug level, and everything trailing the : would be a neutral color. Occassionally, there will also be "FATAL EXCEPTION:", which could maybe have it's own color, just to make it stand out more? Example line of a fatal exception: E/AndroidRuntime(269): FATAL EXCEPTION: main Alternatively, the E/ part could be one color, the name (AndroidRuntime) another, and the bit in parenthesis another... IDK...it would be truly awesome if this could be added...save me a lot of headaches.

Statistics

Installs
233 history
Category
Rating
3.4286 (14 votes)
Last update / version
2013-02-17 / 0.3.4
Listing languages
en

Links