aziz / sublimeansi Goto Github PK

After installing with Package Control, I get this error:

Error loading colour scheme
Packages/User/ANSIescape/tmTheme: Unable to open Packages/User/ANSIescape/tmTheme

Looking in the folder Packages/User/ there is a file named 'ansi'. Inspecting it shows it really has the name 'ansi.sublime-colour-schema'.

I'm using SublimeText 3.0, build 3143 in Windows.

For example this

run { test: 'data' }
Import 1
Import 2
Import 3
�[33mUnitests: �[0mstarted: 1, �[0mfinished: �[32m1, �[0mfailed: �[32m0�[0m

other times it works fine. This is sublime 3 3095.

See https://pypi.python.org/pypi/colored-traceback/0.2.0 .

I got it working with mocha test output, but not this python package. The ANSI escape codes are stripped but no colors appear.

Repro steps:

1. pip install colored-traceback
2. write python script with raise
3. Build in sublime
4. See no colors in traceback output

This is with the public release on package manager.

It's not really clear to me how this can be added by another plugin as a dependency.

Adding a dependencies.json like explained here
https://packagecontrol.io/docs/dependencies doesn't seem to work.

{
  "*": {
    "*": [
      "ANSIescape"
    ]
  }
}

First thanks for the plugin! 👍 I really appreciate being able to read colored log files in the same workflow as my regular editing/etc.

In my current use, I frequently leave a tab open with a log file at all times. But when the file changes on the disk and gets reloaded, the changes jumble up the content and get it into an invalid state that can't be fixed by toggling in/out of ANSI mode. (Closing and reopening the tab works, of course)

Is there an event you can tie into before a reload to revert the style? That's the first solution that comes to my mind, but I know from my limited plugin development that the Sublime API can leave a lot to be desired... If you can't detect reloads, this is way more challenging and probably not worth it, haha.

What do you think about adding editing possibilities to ANSI view?

The biggest issue is to change view back to plain text, since now it's done by simply reverting history.

1. Summary

It would be nice, if SublimeANSI will support font effects (see Font Effects section) as bold, underline and reverse.

2. Argumentation

More features in output. For example, I use bold and underline text in output of my programs.

3. Environment

• Windows 10 Enterprise LTSB 64-bit EN,
• Sublime Text Version 3.1.1, Build 3176 Portable,
• Python 3.7.0,
• ANSIEscape 0.2.5,
• SublimeREPL 2017.01.28.19.13.15.

4. Steps to reproduce

I open SublimeREPL Python Interpreter → I paste this code:

print(u"\u001b[1m SashaBold \u001b[0m\u001b[4m SashaUnderline \u001b[0m\u001b[7m SashaReversed \u001b[0m")

→ Enter.

5. Expected behavior

As in this article:

6. Actual behavior

No effect:

Thanks.

Is there a light theme that would work with this?

The installation instructions in the README.md [on master] are not correct, or there is an issue with the master version..

The instructions references two methods of installation:

1. use Package Control
2. clone the repository (and rename)

At least on my system (ST3/Ubuntu), they yield two different results:

1. creation of Packages/User/ANSIescape, with a ansi.tmTheme (and nothing else)
2. (obviously) cloning of the repository, which has a completely different layout/logic, in particular, there is no ansi.tmTheme.

I have no understanding of the ST[3] plugin structure, but the differences should be at least documented.

This is important, especially because in cases like mine, both installation procedures yield a non-working plugin, in two different ways (I'll file this in two different issues) :-)

Would be very awesome if you could add the 256 color table support:
Example: [38;5;231m

Or even better would be true RGB support.
Thanks alot!

Hi and thx for this module,

The read.me says we have to edit the build config as following :

// someproject.sublime-project
{
    "build_systems":
    [
        {
            /* your existing build command arguments */
            "name": "Run",
            "working_dir": "${project_path}/src",
            "env": {"PYTHONPATH": ".../venv/python2.7/site-packages"},
            "cmd": ["nosetests", "--rednose"],

            /*  add target and syntax */
            "target": "ansi_color_build",
            "syntax": "Packages/ANSIescape/ANSI.tmLanguage"
        }
    ]
}

but with typescript build (included in https://github.com/Microsoft/TypeScript-Sublime-Plugin), target is already defined like that :

{
    "target": "typescript_build",
    "selector": "source.ts, source.tsx"
}

So how to use ANSI colors with typescript build ?

Thx in advance.

I get this error when I try to set the syntax to "ANSI". Error loading colour scheme Packages/User/ANSIescape/ansi.sublime-color-scheme: Unable to find Packages/User/ANSIescape/ansi.sublime-color-scheme

After looking through the closed issues it looks like restarting sublime might fix it: #66 (comment)

This showed up when Sublime Text started:

Traceback (most recent call last):
  File "D:\SublimeText\Data\Packages\ANSIescape\ansi.py", line 237, in check_left_ansi
    if not self._is_view_valid(view):
  File "D:\SublimeText\Data\Packages\ANSIescape\ansi.py", line 271, in _is_view_valid
    if view not in view.window().views():
AttributeError: 'NoneType' object has no attribute 'views'

This seems to coincides with the Overrides Reports package report.

This are the lines:

File: Data/Packages/ANSIescape/ansi.py
266:     def _is_view_valid(self, view):
267:         if view.window() is None:
268:             return False
269:         if view.window() not in sublime.windows():
270:             return False
271:         if view not in view.window().views():
272:             return False
273:         return True

Related:

1. #12 event listener callback error

Copy-and-paste from the build output returns empty. It works when the syntax is set to something else.

Some applications use the BS (backspace, code 08) character to overwrite lines on output. This package could hide these when viewing which cleans up the output.

When the build is proceeding, I still see the "ESC" codes. Then when the build ends, the output takes the right colors.

here's what my sublime-build file looks like

{
    "shell_cmd": "...",

    /*  add target and syntax */
    "target": "ansi_color_build",
    "syntax": "Packages/ANSIescape/ANSI.tmLanguage"
}

See https://github.com/AriaMinaei/pretty-error .

I got it working with mocha test output, but not pretty-error. The ANSI escape codes are stripped but no colors appear.

Repro steps:

sudo npm install pretty-error
node .

Build in sublime (with error in js script)
See no colors in traceback output

This is with the public release on package manager.

Hello !
On my machine tput reset ouputs the string \033(B\033[m.

I've been trying to change the configuration in the ansi.sublime-settings so that the ANSI_FG white scope match it but it doesn't seems to be working... here what I tryed:

      {"scope": "white", "code": "(\\x1b[(]B)?\\x1b\\[(0;)?(37)?m", "color": "#c7c7c7"},
      {"scope": "white", "code": "(\\x1b\\(B)?\\x1b\\[(0;)?(37)?m", "color": "#c7c7c7"},

I pre-pened the original string (which should match the \033[m) and added (\\x1b[(]B)? or (\\x1b\\(B)? to detect the leading part.

This technique is no effective, do you have any idea ?
Thanks a lot!

Description:
When restarting sublime text the ansi escape codes are lost for files that have already been processed by the ansi command. This is occurring because the escape codes are lost from the sublime text "undo" buffer when sublime text is restarted.

Reproduce Issue:

1. Open the file "ansi_test_file.text".
2. Set the syntax to "ANSI" via the sublime text menu.
3. Close and re-open sublime text. (note: the coloring has disappeared)
4. Set the syntax to "Plain Text" via the sublime text menu. (note: the escape codes do not return)

Potential Solution:
On plugin initialization we need to force such files to be reloaded from disk, therefore reloading the lost escape codes. I am currently working on some patches to implement such functionality.

Description:
When executing the undo ansi command on an non-ansi file there is a potential for the user's previous changes to be delete. This occurs because the ansi plugin blindly uses the sublime text undo command to restore deleted escape codes; however if no escape codes have been deleted this will result in the user's previous changes being deleted.

Reproduce Issue:

1. Open a new file.
2. Insert text to the file.
3. Set the syntax to "ANSI" via the sublime text menu.
4. Set the syntax back to "Plain Text" via the sublime text menu. (note: the inserted text will be deleted)

Potential Solution:
We should probably double check view.command_history() before invoking the sublime text undo command to ensure that we are undoing what we think we are undoing.

I'm running ST2 and would like to install your package, but couldn't find it with the Package Control. Do you know if this is also working for ST2?

thnx
viTus

Clang on OSX outputs escape sequences that look like this:

<ESC>[0;1;31m

I don't know escape sequences well enough to know if clang is just flat out wrong, or if it is expecting more complete ANSI support. Either way, the default settings only match color escape sequences with two values.

Here's a mapping that seemed to work for me:

{"scope": "black", "code": "\\x1b\\[(0;(0;)?)?30m", "color": "#000000"},
{"scope": "black_light", "code": "\\x1b\\[(0;)?1;30m", "color": "#686868"},
{"scope": "red", "code": "\\x1b\\[(0;(0;)?)?31m", "color": "#c71e12"},
{"scope": "red_light", "code": "\\x1b\\[(0;)?1;31m", "color": "#ff6f6b"},
{"scope": "green", "code": "\\x1b\\[(0;(0;)?)?32m", "color": "#00c120"},
{"scope": "green_light", "code": "\\x1b\\[(0;)?1;32m", "color": "#67f86f"},
{"scope": "yellow", "code": "\\x1b\\[(0;(0;)?)?33m", "color": "#c7c327"},
{"scope": "yellow_light", "code": "\\x1b\\[(0;)?1;33m", "color": "#fffa72"},
{"scope": "blue", "code": "\\x1b\\[(0;(0;)?)?34m", "color": "#0a2fc4"},
{"scope": "blue_light", "code": "\\x1b\\[(0;)?1;34m", "color": "#6a76fc"},
{"scope": "magenta", "code": "\\x1b\\[(0;(0;)?)?35m", "color": "#c839c5"},
{"scope": "magenta_light", "code": "\\x1b\\[(0;)?1;35m", "color": "#ff7cfd"},
{"scope": "cyan", "code": "\\x1b\\[(0;(0;)?)?36m", "color": "#01c5c6"},
{"scope": "cyan_light", "code": "\\x1b\\[(0;)?1;36m", "color": "#68fdfe"},
{"scope": "white", "code": "\\x1b\\[(0;(0;)?)?(37)?m", "color": "#c7c7c7"},
{"scope": "white_light", "code": "\\x1b\\[(0;)?1;37m", "color": "#ffffff"},
{"scope": "_bold", "code": "\\x1b\\[(0;(0;)?)?1m", "color": "#ffffff", "font_style": "bold"}

It seems plugin doesn't support combined escape sequences. E.g. the following string won't be colorized at all in sublime text by plugin, while Colored should appear with red color on a yellow background.

echo -e "Normal\x1b[31;43mColored\x1b[0mNormal"

Hello,

Using ST3 (build 3083) w/ ANSIescape installed via Package Manager. When trying to use it as part of a build command I see the following error via popup and in console, and no ANSI coloring on the build output:

error: Error loading syntax file "Packages/User/ANSIescape/ANSI.tmTheme": Empty language names are not allowed

I keep getting an error in detect_syntax_change because view == None, but you are referencing it anyway. Please add check to see if view == None and return if True.

    if view == None:
        return

Also, probably should add this check in assign_event_listener as well.

After installing ANSIescape from Package Control and trying to set filetype to ANSI I get this error:

Error loading colour scheme Packages/User/ANSIescape/ansi.tmTheme: Unable to open Packages/User/ANSIescape/ansi.tmTheme

The directory Packages/User/ANSIescape exists but is empty.

Version: Sublime Text 4, build 4107
OS: Debian Stable

Would love your help!

When I select the ANSI language, I get the following error.

Error loading colour scheme Packages/User/ANSIescape/ansi.sublime-color-scheme: Unable to find Packages/User/ANSIescape/ansi.sublime-color-scheme

I'm on ANSIescape version 0.6.3 and Sublime Text 4 (build 4107).

After installing via Package Control, I can choose ANSI as the syntax for my log file, and the escape codes disappear, but there's no color. I get just a black background with white text.

Does the log file use escape codes that are not supported, or is my installation wrong? I'm using Sublime Text 3.2.2, build 3211.

�[0;90;49m
Running test ./spec/site/alarm_spec.rb:2 - RSMP site alarm A0302 detector error (logic error)�[0m
2020-12-16 09:57:52 UTC                           Starting supervisor on port 12111
�[0;95;49m2020-12-16 09:57:52 UTC                           Waiting for site to connect�[0m
2020-12-16 09:57:53 UTC                           Site connected from 127.0.0.1:36592
�[0;94;49m2020-12-16 09:57:53 UTC  KK+AG9998     -->  231f  Received Version message for site KK+AG9998 using RSMP 3.1.2 {"mType":"rSMsg","type":"Version","mId":"231f74a6-137b-47b6-8378-524e3b80a469","siteId":[{"sId":"KK+AG9998"}],"RSMP":[{"vers":"3.1.2"}],"SXL":"1.0.7"}�[0m

Description:
When we open file in new view (File > New view into file) The 2nd view isn't formatted. Changing syntax affects both views syntax, but only in one ANSI colours are displayed.

When setting the target and syntax properties in my build system as stated in the README:

{
"build_systems": [
        {
            "cmd":
            [
                "..."
            ],
            /*  add target and syntax */
            "target": "ansi_color_build",
            "syntax": "Packages/ANSIescape/ANSI.tmLanguage"
        }
    ],
}

the build is broken (does not start) and I have the following output in my ST3 console:

Unable to find target command: ansi_color_build

After installing the plugin, I attempted the same as in the animated screenshot; namely I add a few ansi color codes into a text file and toggle from "plain text" syntax to ANSI.

Although the plugin seems to have been loaded and no errors appear in console, no change seems to happen.

I'm new to ST syntax language/theme files; is there any way to debug what the issue is? Here is some sample content:

�[0;36mtest_something�[0;34m()�[0m
�[0;32m    514 �[0;31m�[0;34m�[0m�[0m
�[0m�[0;32m--> 515 �[0;31m        �[0mself�[0m�[0;34m.�[0m�[0massertEquals�[0m�[0;34m(�[0m�[0mr�[0m�[0;34m.�[0m�[0mstatus_code�[0m�[0;34m,�[0m �[0;36m400�[0m�[0;34m)�[0m�[0;34m�[0m�[0m
�[0m�[0;32m    516 �[0;31m�[0;34m�[0m�[0m
�[0m

Update1: The generated ansi.tmTheme file, just in case you need to have a look at it.

Update2: If I run view.run_command("ansi") in console when the ANSI file view is focused it works nice

Environment:
* Sublime Text Build 3126

A large file (~34MB) takes a minute to load. At first glance it looks like SublimeANSI is broken, especially if you have not used it before.
Sublime Text is blocked, the OS X busy cursor is shown, and Sublime Text is marked "not responding" by OS X.

To reproduce

1. Open a ~34MB logfile, eg. from a rails project, /log/test.log, but probably any large ansi file will do
2. File is loaded fine by sublime text, no issues
3. Switch to ANSI: View -> Syntax -> ANSI
4. Sublime text is blocked, disc activity, takes 40-60 seconds to finish

Expected: Dealing with large ANSI files should not be much slower than for example SQL files. The same file, which also contains lots of SQL statements, works smooth when viewed with "View -> Syntax -> SQL", there is no notable loading time. Trying to parse it as C++ takes a few seconds.

Brief:

I use SublimeANSI to review logging output of my programs. Sometimes I want to review logs when program is still running (and is writing to the log file). ANSI coloring breaks every time file is changed externally and reloaded by Sublime.

Version:

ANSIescape v0.1.5 (from package manager)

Steps to reproduce:

• Open file with ANSI escape sequences in Sublime (e.g. test/ansi_test_file.txt provided in the repository)
• Switch to ANSI syntax
• change file externally: open the same file in another text editor (e.g. Notepad or Atom), change (add newline an the top) and save it; or write into this file programmatically
• Bring Sublime back to focus

Desired behavior:

File contents updates along with ANSI coloring

Observed behavior:

File contents updates, dark ANSI theme is still up, but escape sequences are no longer recognized properly: there are "ESC" signs and colored fragments in random places

Workarounds:

• Switching to plain text and back fixes the colors, but only until the next refresh
• "Auto Refresh" package allows for disabling of the default auto refresh, but this defeats the purpose of real-time logging. Also it is tedious to do so for every file

As suggest by @jfcherng, we should update our current debug logging implementation to use python's logging module. See the commit 98a6727 (Added print verbose debug method) for further information.

Hi,

You said that it was possible to use your plugin as a dependency for build scripts using shell commands , do you have any examples?

Thanks.

Hello,

Before all, thank you for this very useful package :)

I just used it and it appears that i had to change the default settings to see the output with correct colors. Light red and light yellow sere not detected, until i add a ansi.sublime-settings file in my User repo with the following changes :

# default: 
{"scope": "red_light", "code": "\\x1b\\[1;31m", "color": "#ff6f6b"},
{"scope": "yellow_light", "code": "\\x1b\\[1;33m", "color": "#fffa72"},
# user defined :
{"scope": "red_light", "code": "\\x1b\\[31;1m", "color": "#ff6f6b"},
{"scope": "yellow_light", "code": "\\x1b\\[33;1m", "color": "#fffa72"}

Here is a piece of code that did appear red in my shell, and not in Sublime when i redirected it into a file :

�[31;1m{M}�[0m: '...'
�[31;1m{S}�[0m: '...'

Thank you by advance !

The .sublime-build

{
	"shell_cmd": "tape ./index.js | tap-summary --no-progress",
	"working_dir": "${file_path}",
	"selector": "source.js",
    "target": "ansi_color_build",
    "syntax": "Packages/ANSIescape/ANSI.tmLanguage"
}

The links:

https://github.com/substack/tape

https://github.com/zoubin/tap-summary

Different projects use different build tools, and it may be useful to override setting per-project. Looking at a different project's source, this is probably as simple as calling view.window().project_data().get('SublimeANSI'), with appropriate None checks.

Since this commit 1fcbbe5 the "Packages/ANSIescape/ANSI.tmLanguage" file was replaced with "Packages/ANSIescape/ANSI.sublime-syntax".

This has change has not been reflected in the documentation in the README.md

Hello,

I am running ANSI syntax/color scheme. weird ANSI escape codes disappeared but the text color did not change. I did not change anything in default ansi.sublime-settings.
Any idea what the problem could be?

Thanks,
Emre

Originally posted on: rctay/sublime-text-buildview#24

This plugin is doing the output panel to be read-only, when I am setting the target build as ansi_color_build & Packages/ANSIescape/ANSI.tmLanguage on my .sublime-build file.

File example:

    "build_systems":
    [
        {
            "working_dir": "$project_path/installers",

            "name": "Galileo Installer",
            "cmd": ["galileo.bat", "$project_path/plugins/addons/amxmodx/scripting/galileo.sma", "galileo", "$packages"],

            "target": "ansi_color_build",
            "syntax": "Packages/ANSIescape/ANSI.tmLanguage",
        },
    ]

It appears that the view validation that was introduced in commits b5ceb21 and 143a6f8 may be a little too aggressive. It turns out that view.window will be set to None while a tab is being shifted from one position to another. This somewhat makes sense, as the view doesn't really belong to any specific window while it is being moved around.

The problem is that _is_view_valid is invoked while the view is being moved; hence it sees view.window == None and assumes the view is invalid (thus removing the ansi event listeners). As a result, views that have been moved will no longer respond to syntax changes via the sublime menu.

I have some log files that have CSI characters which are showing up in my logs. Perhaps parsing should be added to remove these.

[ESC]SC[0Ktravis_fold:end:services
[ESC][0Ktravis_fold:start:postgresql
[ESC][0Ktravis_time:start:121e4528
[ESC][0K$ travis_setup_postgresql 9.6
Starting PostgreSQL v9.6[ESC][0K
 * Stopping PostgreSQL 9.2 database server       [ESC][80G 
[ESC][74G[ OK ]
 * Stopping PostgreSQL 9.3 database server       [ESC][80G 
[ESC][74G[ OK ]
 * Stopping PostgreSQL 9.4 database server       [ESC][80G 
[ESC][74G[ OK ]
 * Stopping PostgreSQL 9.5 database server       [ESC][80G 
[ESC][74G[ OK ]

I tried adding the following into ansi.sublime-settings but it did not work:

      {"scope": "_bold", "code": "\\x1b\\[0K", "color": "#ffffff"},
      {"scope": "_bold", "code": "\\x1b\\[K", "color": "#ffffff"},

Is there any way to add custom highlight for not only the ANSI color escape symbols?
It could be useful to highlight special words in the console build captured log like: "error", "warning", "note", "start", "end", "make", "time," etc.

Coloring of the text disappeared. Ubuntu-18, ST-3207. Previously worked. After installing manually and switching to commit b97ea0e the problem disappears. Tested on two computers at home and at work. I would like to get rid of manual rollback of the package.

This GIF shows the issue

https://i.gyazo.com/4151e11a78b83a31e58a9010cd2e2333.mp4

My build system looks like this:

`{
"target": "ansi_color_build",
"syntax": "Packages/ANSIescape/ANSI.tmLanguage",

"shell_cmd": "my commands"                                                                                                                                        

}
`

In these lines we are replacing unsupported ANSI codes:

Is is necessary? We remove them later, during looking for ANSI colour codes this replacement shouldn't change much. Am I missing something?

Changing to ANSI on large files crashes ST3, might just be worth indicating the upper limit on file size in documentation, still a very useful tool. Thanks.