1. Brugerprofil
  2. Carlos Rodriguez

Dine kommentarer

OSX: double/triple-click+hold doesn't work as expected
This is a regression bug that made it's way into Build 2182.
13 år siden
Tab Settings Not Respecting User Settings
Jon,

I think I see an issue. I'm not sure if the the API changed, but the key that I had was translate_tabs_into_spaces, but it looks like the key is now translate_tabs_to_spaces.
13 år siden
Tab Settings Not Respecting User Settings
Jon,

I still think something is not right.

Here are the contents of my Preferences.sublime-settings file:

{
"auto_complete": false,
"color_scheme": "Packages/Color Scheme - Default/Monokai.tmTheme",
"draw_indent_guides": false,
"file_exclude_patterns":
[
"*.pyc",
"*.pyo",
"*.exe",
"*.dll",
"*.obj",
"*.o",
"*.a",
"*.lib",
"*.so",
"*.dylib",
"*.ncb",
"*.sdf",
"*.suo",
"*.pdb",
"*.idb",
"*.DS_Store",
"*.pdf",
"*.class",
"*.jpg",
"*.gif",
"*.png"
],
"fold_buttons": false,
"folder_exclude_patterns":
[
".svn",
".git",
".hg",
"CVS",
"log",
"sphinx",
"vendor/ruby"
],
"font_options":
[
"subpixel_antialias"
],
"highlight_line": true,
"hot_exit": false,
"ignored_packages":
[
"Vintage"
],
"detect_indentation": false,
"remember_open_files": false,
"tab_size": 2,
"translate_tabs_into_spaces": true,
"theme": "Soda Dark.sublime-theme",
"trim_trailing_white_space_on_save": true
}

As you can see I have detect_indentation as false, my tab_size is set to 2 and translate_tabs_to_spaces is set to true.

Looking in the documentation, the order for tab spaces is thus:
  1. Packages/Default/Base File.sublime-settings
  2. Packages/Default/Base File (<platform>).sublime-settings
  3. Packages/User/Base File.sublime-settings
  4. Packages/<syntax>/<syntax>.sublime-settings
  5. Packages/User/<syntax>.sublime-settings
I don't have any syntax specific settings for Ruby files, yet when I open a Ruby file in a project, it defaults not to use spaces instead of tabs. You can see in this screenshot this is not happening:

13 år siden
command_history does not help determine last command
The command history did indeed change.

I'm having an issue with my plugin as well (https://github.com/eddorre/SublimeERB/issues/6)

It looks like the API for the command history has

changed a bit.


In the stable release of Sublime Text, when running my command, the

command history (self.view.command_history) is listed as such:


(None, None, 0)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)

COMMAND HISTORY

(u'erb', None, 1)


As you can see this allows me to find out of they have not done

anything else in between key presses which allows me to toggle ERB

blocks.


In the latest dev build, the command history looks something like this:


COMMAND HISTORY

(None, None, 0)

COMMAND HISTORY

(None, None, 0)

COMMAND HISTORY

(u'erb', None, 2)

COMMAND HISTORY

(u'erb', None, 2)

COMMAND HISTORY

(u'left_delete', None, 1)

COMMAND HISTORY

(u'left_delete', None, 1)

COMMAND HISTORY

(u'left_delete', None, 1)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 3)

COMMAND HISTORY

(u'erb', None, 6)

COMMAND HISTORY

(u'erb', None, 6)

13 år siden


Kundesupport af UserEcho