Hi,

I'm using inno setup and I'd love to edit the files in code with fun colors. How do I get your pascal tool to recognize iss files?

Two issues with the initial release:

1. The parameters are not available (package.json error)
2. The JCF formatter is running for folders by default. (It should be forced to files -F )

Add Go to Symbol

The idea is to have telemetry for things like:

• most executed commands - to understand how many commands are useless
• common user settings - to understand if any setting should have its default value changed
• activity bar usage - to understand if it was a good idea to create that UI
• context menu usage - to understand how many commands are useless
• OS platform - to know if my Windows machine is enough

When an error occurs while formatting code, specially when using Jedi Code Format, the message displayed does not say much information. Mostly because the showErrorMessage API only displayes one line.

Find a way to display the console error so the user can detect what has happened, without needing to look at the Developer Tool / Console.

I created the tasks.json but when i try to Run Task Build I get "The filename, directory name, or volume label syntax is incorrect."

"command": "‪C:\FPC\3.0.2\bin\i386-win32\fpc.exe"

"args": ["‪C:\Users\me\Desktop\helloworld.pas"]

Is maybe something wrong with my paths?

It is a normal keyword also today, so it does not highlight as keyword.control

Every time you open a .pas file this warning comes out in the visual studio code.
I had to uninstall the plugin because it was very annoying.

More info:

• https://code.visualstudio.com/blogs/2019/05/02/remote-development
• https://code.visualstudio.com/api/advanced-topics/remote-extensions

workspace.fs API available in VS Code 1.37 - July 2019

• https://code.visualstudio.com/updates/v1_37#_extension-authoring

While developing the PR to add Pascal support in Monaco Editor, I have noted some errors in the current grammar. Also, a few updates could be made to add new features recently added in VS Code.

News Features / Updates

• Add code folding for $REGION
• Add < > as AutoClosingPair and SurroundingPairs
• Add "hex" as a new identifier for numbers
• Add #number as a valid string pattern

Fixes

• Remove " (doublequotes) as AutoClosingPair and SurroundingPairs
• 0x is not a valid number pattern
• -- is not a valid line comment pattern (like previoulsy fixed in Atom)
• "..." (doublequotes) is not a valid string pattern

I installed everything by Homebrew. the environmental variables are set as below:
declare -x GTAGSCONF="/usr/local/Cellar/global/6.5.7/share/gtags/gtags.conf" declare -x GTAGSLABEL="pygments"
declare -x PATH="/usr/local/Cellar/global/6.5.7/bin:/usr/local/Cellar/ctags/5.8_1:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" declare -x PWD="/Users/Administrator/Documents/Pascal"
but when I run the gtag command, the result was less than satisfactory:
Traceback (most recent call last): File "/usr/local/Cellar/global/6.5.7/share/gtags/script/pygments_parser.py", line 27, in <module> import pygments.lexers ImportError: No module named pygments.lexers gtags: unexpected EOF.

So what causes this problem? Is that about the operating system I used? Is there any way to fix it?

After installing dependencies (GNU Global, ctags, gtags, python and pygments), reloading everything and editing *.pas, I keep getting following error in VSC:

Some error occured: Error: Command failed: gtags 
gtags: directory '' not found.

Consequently, I cannot harness extension's code navigation.

OS: Ubuntu 20.04 (Linux x64 5.4.0-31-generic)
Visual Studio Code: 1.45.1

MAD-Pascal commonly used file extention for included files is .inc.
Please add it to the list in package.json.

Regex pattern uses ".p" file extension, but the ".pas" is commonly used.

-                "regexp": "^([\\w]+\\.p)\\((\\d+)\\,(\\d+)\\)\\s(Fatal|Error|Warning|Note):(.*)",
+                "regexp": "^([\\w]+\\.pas)\\((\\d+)\\,(\\d+)\\)\\s(Fatal|Error|Warning|Note):(.*)",

Maybe change or add this extension too?

Instead of copy/pasting the same build tasks into tasks.json for every pascal project folder that a user has, have you found any way to automate the process?
For example: A user has a fully functional build script that points to DCC32.exe, is there a way for the extension to automatically create a tasks.json with those parameters to each created pascal project?

Add Peek Definition

Hey, i got some troubles in configuring the run build task in the tasks.json file, can you please give an example for it, or may be a tutorial video for it? Maybe you could also make the whole installation tutorial if you want to.
Also, i can't seem to configure debugging for it, any help please?
Thanks

First,I don't know what does 'update two tags' exactly mean. What should I do to update it? Is that correct to create two new files?
Also, when i run the command Pascal:Generate Tagsin VS Code ,it returnsSome error occured: Error: Command failed: gtags . But when I run gtags in Terminal in the root folder, it works fine and creates three new files in the folder. So is that a bug?
When I run Pascal:update Tags in VS Code, it returnsThe tags where updated. I was confused.I do not even understand what that means.
And, it seems that I cannot 'Peek Defination' although you added that feature in README. The software returns 'Defination not found.'
So would you tell me what exactly should I do to debug and run Pascal project in VS Code? And how to enable code navigation?Thanks

Add Go to Definition

January 2020 (1.42)

• https://code.visualstudio.com/updates/v1_42#_extensions-view-context-menu

Hi, I maintain VS Code's Webview API

Issue

Our telemetry suggests that your extension uses webviews and may be loading resources in these webviews using hardcoded vscode-resource: URIs. These URIs have some important limitations and don't work properly when VS Code is run in a browser. We are also making changes in the desktop version of VS Code that may cause these URIs to not work properly in future versions of VS Code.

While we are making our best effort to continue support existing webview extensions that use vscode-resource: URIs on desktop versions of VS Code, we will not able to fully support all uses cases.

Fix

To ensure that your extension continues to work in as many environments as possible—including on web and remotely—please:

• Switch to use the Webview.asWebviewUri function for loading resources.

• Switch to use the Webview.cspSource property in content security policies.

These APIs shipped around 2 years ago so they should be available in all modern versions of VS Code. You can find additional information about the issue here: microsoft/vscode#97962

Let me know if you have any questions about this change

https://code.visualstudio.com/api/advanced-topics/tslint-eslint-migration

Use my eslint-config-vscode-ext shared config (https://www.npmjs.com/package/eslint-config-vscode-ext)

All of the block comment controls don't operate, (default ctrl + /).
Any chance we could get that fixed?

Hello!

Do you plan to add support for completion support in the near future?

Thanks!

Please add this code to tasks.json snippet for FreePascal so it can be used in Linux:

 		"windows": {
 			"command": "FPC.EXE_PATH"
 		},
+		"linux": {
+			"command": "fpc"
+		},

And maybe change "args": ["YOUR_FREEPASCAL_PROJECT"] to the "args": ["${relativeFile}"] so the task will compile the current opened file?

June 2019 (1.36)

• https://code.visualstudio.com/updates/v1_36#_splitting-vscode-package-into-typesvscode-and-vscodetest
• https://code.visualstudio.com/api/working-with-extensions/testing-extension#migrating-from-vscode

More info: http://code.visualstudio.com/blogs/2017/02/08/syntax-highlighting-optimizations

• {$...}
• Assert

alefragnani/vscode-pascal-formatter#7

• Issue Type: Bug
• Extension Name: pascal
• Extension Version: 8.0.2
• OS Version: Linux x64 5.0.0-26-lowlatency
• VSCode version: 1.35.0

⚠️ We have written the needed data into your clipboard. Please paste! ⚠️

{
	"messages": [],
	"activationTimes": {
		"startup": true,
		"codeLoadingTime": 10,
		"activateCallTime": 1,
		"activateResolvedTime": 163,
		"activationEvent": "*"
	},
	"runtimeErrors": []
}

Hi! I forked you project to make a support for «Component Pascal» aka «BlackBoxComponentBuilder».
Actually I have a syntax highlight working already, but due to its dynamic nature blackbox allows to do interesting things like dynamic completion from RTTI and so on. This is in a far future...
Meanwhile It looks like you forgot to add some files to git, like src/whats-new/* and vscode-whats-new/*

Now trying to disable all references to missing files...

If the user asks for language services but the tags were not yet generated.

Increase the support other Programmatic Language Features available in VS Code, which makes IntelliSense experience so great.

Currently, the extension only supports a few set of features:

• Document Symbols (only methods) - https://code.visualstudio.com/Docs/editor/editingevolved#_go-to-symbol
• Definition - https://code.visualstudio.com/Docs/editor/editingevolved#_go-to-definition
• References - https://code.visualstudio.com/Docs/editor/editingevolved#_peek
• Bracket Matching - https://code.visualstudio.com/Docs/editor/editingevolved#_bracket-matching
• Errors and Warnings (via Tasks) - https://code.visualstudio.com/Docs/editor/editingevolved#_errors-warnings
• Document Formatting (via Pascal Formatter extension) - https://code.visualstudio.com/docs/editor/codebasics#_formatting

There are another set of features which would make the coding experience even richer.

• Document Symbols (other kind of symbols, like variables, constants, etc)
• Go to Implementation - https://code.visualstudio.com/Docs/editor/editingevolved#_go-to-implementation
• Reference Information - https://code.visualstudio.com/Docs/editor/editingevolved#_reference-information
• Rename Symbol - https://code.visualstudio.com/Docs/editor/editingevolved#_rename-symbol
• Code Actions - https://code.visualstudio.com/Docs/editor/editingevolved#_code-action
• Code Completions
• Signature Help
• Code Folding - https://code.visualstudio.com/docs/editor/codebasics#_folding

More info:

• https://code.visualstudio.com/api/language-extensions/programmatic-language-features
• https://code.visualstudio.com/docs/editor/intellisense
• https://code.visualstudio.com/docs/editor/editingevolved
• https://code.visualstudio.com/docs/editor/refactoring

When the extension updates, it opens a popup to tell you what is new. Most extensions don't do that. You should either disable the update popup, or add a way to optionally disable it.

Hi! I have an issue with symbols navigation and I am not sure whether this is configuration or something with the extension: I have configured global (with ctags, pygments etc.) and it seems to be working correctly. I can see the symbols table is building correctly (e.g. with gtags -v --explain) and dump symbols (e.g. with gtags -d GRTAGS) but they do not appear in any of VSCodes lists: that is when I press Ctrl+T (#) or Ctrl+P (@) etc.

Am I doing something wrong? Is there anything else I can test to determine whether something is wrong with my configuration or is it something with the extension?

Syntax Highlighter: CodeTyphon FileExtension *.ppr doesn't work

Does debug work with FPC?

Hello, thanks for the great work first.

I am new to these tagging tools. I noticed that navigation only works for procedure and function, not variable. I've tried to use the global -f command and there is no variable. So is my configuration wrong or this is the supposed behavior? I've tried to built Pygments Plug-in Parser for GLOBAL, but it din't work.

Hi! Can I define a new syntax highlighting?
Or is there a file in your extension that holds the highlighted syntax?

https://code.visualstudio.com/updates/v1_45#_deprecating-and-archiving-of-the-vscode-npm-module

Better syntax definitions

• basic types
• hexa values
• includes
• properties
• modifiers
• operators
• flow control

I'm testing Visual Studio Code now (1.21.1 for Mac) and got it working just fine using C++ (debugging, building, breakpoints). Now I'm trying to setup a Pascal project using the extension "Language Pascal" but breakpoints seem to be entirely disabled, i.e. clicking in gutter doesn't toggle anything, "Debug > Toggle Breakpoint" menu doesn't work either (nothing is added in the breakpoints pane).

Is this a bug or does the extension have to explicitly opt into breakpoints? Creating a new empty file has breakpoints disabled also so maybe I'm missing something.

Sorry if this is a bad place to ask questions but I didn't know where else to go. Thanks in advance.

https://github.com/alefragnani/vscode-language-pascal/network/alert/package-lock.json/tar/open

Some of the auto complete does not work well.

Example:
When I type
if ... then
Then I pressed enter, the enter key will be eaten.
What I want is skip to the next line with indent.
This only happens when I pressed the enter key second time.

Besides, the snippet of begin...end is bad.
It inserts two position, one between begin end and one after the end keyword.
However, when I type code between begin end, the auto complete function will not work at all. There will be no hint at all.

Also, can you make a option to capitalize the first letter of keywords?
For example, when I type "if" then pressed space, the "if" keyword will become "If"

Lastly, it will be good if the main begin end will be automatically insert the dot instead of a semicolon.

Doing so would make this pieces move alone, with no dependency from the language itself.

Of course that this extension (Pascal) would require both, and for that I could use extensionDependencies. This means no difference for current users.

• Formatter Pascal Formatter
• Snippets

https://code.visualstudio.com/updates/v1_31#_open-resources-in-a-browser

Based on withProgress API

Add Find all References

Since gtags fails to work well for huge projects when all features are requested (Declarations and References), there should be a way to still use at least for Go to Symbols in File, as it was used at the beginning of the projects.

Let's create a setting for that.