DEV Community: Janko

test kodu

Janko — Sun, 08 Mar 2026 18:18:34 +0000

Toto je ukazka kodu:

javascript
alert('ahoj');

How to Fix GitHub Copilot Terminal Integration in VS Code

Janko — Thu, 05 Feb 2026 16:04:54 +0000

If your GitHub Copilot Chat is failing to send commands to the terminal or constantly asking for permission, follow these steps to fix your settings.json.

1. Enable Shell Integration

Copilot cannot interact with the terminal without this.

Change in settings.json:
"terminal.integrated.shellIntegration.enabled": true

2. Relocate Chat for Stability

Running Chat in the terminal panel often causes focus issues. Use the Sidebar instead.

Change in settings.json:
"github.copilot.chat.terminalChatLocation": "chatView"

Summary for settings.json

{
"terminal.integrated.shellIntegration.enabled": true,
"github.copilot.chat.terminalChatLocation": "chatView",
}

Enhancing Todo Tree in VS Code

Janko — Sun, 04 Jan 2026 20:56:02 +0000

Todo Tree collects inline TODO/FIXME-style comments from your code and shows them in a compact tree view in VS Code. Below is a concise explanation of useful settings and why they help.

Group items in the tree (todo-tree.tree.grouped) to organise by file or tag for faster navigation.
Enable grouping buttons (todo-tree.tree.buttons.groupByTag, groupBySubTag) to quickly switch views.
Define a clear set of tags in todo-tree.general.tags (e.g. TODO, FIXME, [ ], @urgent) so filtering is predictable.
Use todo-tree.highlights.customHighlight to colour-code priorities or owners, making high-priority items stand out.
Adjust the todo-tree.regex.regex to match your comment styles across languages (line comments, block comments, markdown lists, etc.).
Limit scope by excluding large folders or node_modules so the tree stays relevant and responsive.

Example settings.json snippets (adapt to your preferences):

"todo-tree.tree.tagsOnly": true,
  "todo-tree.tree.grouped": true,
  "todo-tree.tree.buttons.groupByTag": true,
  "todo-tree.tree.buttons.groupBySubTag": true,
  "todo-tree.general.tags": [
    "[ ]",
    "[/]",
    "@jankoweb",
    "TODO",
    "FIXME",
    "@1",
    "@2",
    "@3",
    "@4"
  ],
  "todo-tree.regex.regex": "(//|#|<!--|;|/\\*|^|^[ \\t]*\\*|^[ \\t]*(-|\\d+.))\\s*($TAGS)",
  "todo-tree.regex.regexCaseSensitive": false,
  "todo-tree.filtering.includeGlobs": ["**/*.todo", "**/*.td"],
  "todo-tree.filtering.excludeGlobs": ["**/node_modules/*/**"],
  "todo-tree.tree.labelFormat": "${afterOrBefore}",
  "todo-tree.highlights.customHighlight": {
    "[ ]": { "foreground": "green" },
    "[/]": { "foreground": "yellow" },
    "[x]": { "foreground": "silver" },
    "@jankoweb": { "foreground": "magenta" },
    "TODO": { "foreground": "green" },
    "FIXME": { "foreground": "lime" },
    "@1": { "foreground": "red" },
    "@2": { "foreground": "orange" },
    "@3": { "foreground": "yellow" },
    "@4": { "foreground": "blue" }
  },
  "todo-tree.highlights.defaultHighlight": {
    "type": "whole-line"
  }

Workflow tips: keep tag names short and consistent, include owner prefixes when helpful, and combine Todo Tree with your issue tracker for lifecycle management. The result is faster code navigation and clearer visibility into outstanding work.

Automating DEV.to Publishing with GitHub Actions

Janko — Sun, 04 Jan 2026 00:04:30 +0000

GitHub Actions can automate publishing your markdown articles to DEV.to whenever you push changes to your repository.

What You Need

A GitHub repository with your articles in a posts/ folder (markdown files with front matter).
DEV.to API key stored as a GitHub secret named DEVTO_API_KEY.
The workflow file (.github/workflows/publish.yml) with the following configuration:

name: Publish to dev.to

on:
  push:
    branches:
      - main
    paths:
      - "posts/**/*.md"

permissions:
  contents: write

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Get changed posts
        id: changed
        run: |
          if git rev-parse HEAD~1 >/dev/null 2>&1; then
            FILES=$(git diff --name-only HEAD~1 HEAD \
              | grep '^posts/.*\.md$' \
              | tr '\n' ' ')
          else
            FILES=$(git show --name-only --pretty="" HEAD \
              | grep '^posts/.*\.md$' \
              | tr '\n' ' ')
          fi
          echo "FILES=$FILES" >> $GITHUB_OUTPUT

      - name: Publish articles to dev.to
        if: steps.changed.outputs.FILES != ''
        uses: sinedied/publish-devto@v2
        with:
          devto_key: ${{ secrets.DEVTO_API_KEY }}
          github_token: ${{ secrets.GITHUB_TOKEN }}
          files: ${{ steps.changed.outputs.FILES }}
          conventional_commits: true

This setup automatically publishes your articles to DEV.to when you commit changes to markdown files in the posts directory.

Creating a Reliable VS Code Task for New DEV.to Posts (Windows + PowerShell)

Janko — Sat, 03 Jan 2026 23:09:03 +0000

This article provides a verified setup for creating new DEV.to posts using VS Code Tasks on Windows with PowerShell.

It avoids common issues with input handling and quoting.

Problem

Using tasks.json with type: "shell", inline PowerShell, and ${input:...} directly in scripts causes VS Code to expand inputs without escaping. Spaces in input break PowerShell parsing, leading to errors like "Missing statement block" or broken arrays.

Launch Configuration

To run the task with F5 without debug UI:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Run Task",
      "type": "node",
      "request": "launch",
      "program": "echo",
      "args": ["Task completed"],
      "preLaunchTask": "New DEV.to post (today)",
      "noDebug": true,
      "console": "internalConsole",
      "internalConsoleOptions": "neverOpen"
    }
  ]
}

Key Principles

Avoid interpolating ${input:...} directly into PowerShell.
Use type: "process", not shell.
Pass input via environment variables ($env:VAR_NAME).

This is the robust approach for Windows.

Working `tasks.json`

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "New DEV.to post (today)",
      "type": "process",
      "command": "pwsh",
      "args": [
        "-NoProfile",
        "-Command",
        "$ErrorActionPreference='Stop'; $d=Get-Date -Format 'yyMMdd'; $n=$env:POST_NAME; if ([string]::IsNullOrWhiteSpace($n)) { $fname=('{0}.md' -f $d) } else { $fname=('{0} {1}.md' -f $d, $n) }; $dir=Join-Path $PWD 'posts'; if (!(Test-Path $dir)) { New-Item -ItemType Directory -Path $dir | Out-Null }; $f=Join-Path $dir $fname; if (!(Test-Path $f)) { @('---','title: ""','published: false','tags:','---','') | Set-Content -Encoding utf8 $f }; code -r $f"
      ],
      "options": {
        "cwd": "${workspaceFolder}",
        "env": {
          "POST_NAME": "${input:postName}"
        }
      },
      "group": "build",
      "problemMatcher": []
    }
  ],
  "inputs": [
    {
      "id": "postName",
      "type": "promptString",
      "description": "Enter post name (optional):",
      "default": ""
    }
  ]
}

Task Behavior

Prompts for optional post name.
Creates file: yyMMdd.md or yyMMdd Name.md.
Ensures posts/ directory exists.
Adds DEV.to front-matter if new.
Opens file in VS Code.

Why It Works

type: "process" avoids shell re-parsing.
Environment variables handle spaces safely.
PowerShell gets valid syntax.

Stable and safe for production.

Recommendations

Use extensions for slugifying filenames.
Auto-fill title from filename.
Set published: true for posts.

Conclusion

For VS Code + PowerShell on Windows, this is the correct way to handle inputs in tasks.json. Other methods will break.

Automating Git Workflow in VS Code: AI Commit & Sync with One Shortcut

Janko — Thu, 01 Jan 2026 20:39:08 +0000

Automating Git Workflow in VS Code: AI Commit & Sync with One Shortcut

Manually staging files, waiting for AI to generate a commit message, and then pushing can be tedious. While extensions like GitLens Pro offer this, you can achieve the same "one-click" workflow for free using GitHub Copilot and the Macro Commander extension.

Prerequisites

To use this automation, ensure you have the following installed:

GitHub Copilot (for AI message generation)
Macro Commander (jeff-hykin.macro-commander)

Step 1: Define the Macro in `settings.json`

Open VS Code Settings (JSON): Ctrl+Shift+P → Preferences: Open User Settings (JSON).

Add the following configuration:

"macros": {
    "aiCommitSmart": [
      {
        "javascript": [
          "const sleep = (ms) => new Promise(r => setTimeout(r, ms));",
          "const gitExt = vscode.extensions.getExtension('vscode.git');",
          "if (!gitExt) { await vscode.window.showErrorMessage('Git extension not found'); return; }",
          "const api = gitExt.exports.getAPI(1);",
          "const repo = api.repositories?.[0];",
          "if (!repo) { await vscode.window.showErrorMessage('No Git repository in this window'); return; }",
          "",
          "await vscode.commands.executeCommand('git.stageAll');",
          "await vscode.commands.executeCommand('workbench.view.scm');",
          "await vscode.commands.executeCommand('github.copilot.git.generateCommitMessage');",
          "",
          "let committed = false;",
          "const oldHead = repo.state.HEAD?.commit;",
          "for (let i = 0; i < 300; i++) {",
          "  const msg = repo.inputBox.value;",
          "  if (msg && msg.trim().length > 0) {",
          "    await sleep(300);",
          "    await vscode.commands.executeCommand('scm.acceptInput');",
          "    // wait for HEAD to change or for index/worktree to be clean",
          "    for (let j = 0; j < 100; j++) {",
          "      const head = repo.state.HEAD?.commit;",
          "      const indexChanges = repo.state.indexChanges ? repo.state.indexChanges.length : 0;",
          "      const workingChanges = repo.state.workingTreeChanges ? repo.state.workingTreeChanges.length : 0;",
          "      if ((head && oldHead && head !== oldHead) || (indexChanges === 0 && workingChanges === 0)) {",
          "        committed = true;",
          "        break;",
          "      }",
          "      await sleep(100);",
          "    }",
          "    break;",
          "  }",
          "  await sleep(100);",
          "}",
          "",
          "if (!committed) {",
          "  await vscode.window.showWarningMessage('AI Commit: timeout waiting for message or commit. Will attempt to stash and pull.');",
          "  try {",
          "    await vscode.commands.executeCommand('git.stash');",
          "  } catch (e) {",
          "    // ignore stash errors",
          "  }",
          "  await sleep(500);",
          "  try {",
          "    await vscode.commands.executeCommand('git.pullRebase');",
          "  } catch (e) {",
          "    await vscode.window.showErrorMessage('Pull failed: ' + (e && e.message ? e.message : e));",
          "  }",
          "  try {",
          "    await vscode.commands.executeCommand('git.stashPop');",
          "  } catch (e) {",
          "    // ignore stash pop errors",
          "  }",
          "  return;",
          "}",
          "",
          "await sleep(500);",
          "// final safety check: if repo still has changes, stash, pull, pop",
          "const indexChanges = repo.state.indexChanges ? repo.state.indexChanges.length : 0;",
          "const workingChanges = repo.state.workingTreeChanges ? repo.state.workingTreeChanges.length : 0;",
          "if (indexChanges > 0 || workingChanges > 0) {",
          "  try {",
          "    await vscode.commands.executeCommand('git.stash');",
          "  } catch (e) {}",
          "  await sleep(300);",
          "  try {",
          "    await vscode.commands.executeCommand('git.pullRebase');",
          "  } catch (e) {",
          "    await vscode.window.showErrorMessage('Pull failed: ' + (e && e.message ? e.message : e));",
          "  }",
          "  try {",
          "    await vscode.commands.executeCommand('git.stashPop');",
          "  } catch (e) {}",
          "} else {",
          "  await sleep(200);",
          "  await vscode.commands.executeCommand('git.push');",
          "  await sleep(500);",
          "  await vscode.commands.executeCommand('git.pullRebase');",
          "}"
        ]
      }
    ]
  }

Step 2: Map the Keyboard Shortcut

Open Keyboard Shortcuts (JSON): Ctrl+Shift+P → Preferences: Open Keyboard Shortcuts (JSON).

Add this binding:

{
  "key": "ctrl+alt+g",
  "command": "macros.aiCommitSmart"
}

Step 3: Reload VS Code

Ctrl+Shift+P → Reload Window

How It Works

Once configured, simply press Ctrl + Alt + G. VS Code will:

Stage all your current changes.
Open the SCM view.
Call GitHub Copilot to write a commit message based on your diff.
Wait (up to 30 seconds) for the AI to fill in the message.
Commit the changes automatically.

This setup transforms a 5-step manual process into a single, seamless action.

Notes

Works only if:
- A Git repository is active
- You are signed in to GitHub Copilot
Timeout is about 30 seconds
Fully compatible with Settings Sync

HTTrack Website Copier – Troubleshooting gzip Errors

Janko — Tue, 30 Dec 2025 00:24:42 +0000

HTTrack is a free, open-source offline browser utility. Download sites for offline viewing: httrack.com

Issue:
HTTrack sometimes fails to decompress (unzip) downloaded pages on jankoweb, resulting in corrupted binary output instead of HTML.

Observed error:

Error when decompressing
while fetching pages that appear to be gzip-compressed.

Workaround:
In HTTrack, go to:
Set Options → Spider → Force HTTP/1.0

Why?
Forcing HTTP/1.0 disables some server-side compression/transfer behaviors that may trigger decompression failures in HTTrack.

Status:
Testing whether HTTP/1.0 prevents broken gzip responses from the server.

VS Code Terminal Shell Integration (Windows)

Janko — Tue, 30 Dec 2025 00:19:11 +0000

To avoid “The terminal is awaiting input” and similar prompts, VS Code needs Terminal Shell Integration enabled and a supported shell.

Problem:
If you see “The terminal is awaiting input” or similar prompts, VS Code needs Terminal Shell Integration enabled and a supported shell.

Required VS Code settings (settings.json):

{
    "terminal.integrated.shellIntegration.enabled": true,
    "terminal.integrated.defaultProfile.windows": "PowerShell 7",
    "terminal.integrated.profiles.windows": {
        "PowerShell 7": {
            "path": "C:\\Program Files\\PowerShell\\7\\pwsh.exe"
        }
    }
}

After changing settings:

Close all terminals
Reload VS Code window

Still seeing the message?
You are likely using Windows PowerShell 5.1, which has unreliable shell integration.

Fix (one-time per machine):

Install PowerShell 7:
- Microsoft Docs
- Or run:
```
winget install Microsoft.PowerShell
```

PowerShell 7 fully supports VS Code terminal integration and resolves command/input detection issues.

Moved from https://jankoweb.tumblr.com/

Janko — Mon, 29 Dec 2025 23:58:13 +0000

I'm moving from Tumblr to Dev.to!

Why?

Markdown support – writing technical posts is much easier
GitHub integration – write and manage articles in Visual Studio Code

Follow me here for new content about programming and web development!

Coronavirus stats: worldwide country position bookmarklet

Janko — Wed, 06 Jan 2021 16:50:16 +0000

javascript:
void( 
document.body.onclick = async function (event) {
 event = event || window.event;
 var element = event.target || event.srcElement;
 await new Promise(resolve => setTimeout(resolve, 10));
 state = 'Czechia'; /* CHANGE THIS TO SEE OTHER STATE */
 index = document.body.innerText.search(state);
 place = document.body.innerText.substring(index - 4,index).match(/\n([0-9]+)/);
 alert(state + ' is #' + place[1] + ' in ' + element.textContent + ' worldwide.')} );

Simply add this code in place of a bookmark URL -

Go to https://www.worldometers.info/coronavirus/ and click this bookmark. Then - when you click on the first row of the data table with data

the bookmarklet will show you the position of the selected country (see in code)

Bookmarklet for hashtags insertion on social networks

Janko — Sat, 12 Dec 2020 13:33:14 +0000

1) Put this code in place of URL of your bookmark:

javascript:document.execCommand('insertText', false /*no UI*/, "#education #science #popularization");

2) When you typing text into an editable (social networks etc.) array click on the created bookmark
3) Javascript put hashtags
You can change hashtags as you like and create other bookmarks with different hashtags.

Notes

Twitter - you have to start typing text (or an error occures).

Tested on

Google Chrome

Inspired by

https://kubyshkin.name/posts/insert-text-into-textarea-at-cursor-position/

SOLVED: Cisco Anyconnect Linux Mint 20 SIGSEGV

Janko — Mon, 07 Dec 2020 13:46:50 +0000

I/O warning : failed to load external entity "/opt/cisco/anyconnect/CustomerExperienceFeedback/CustomerExperience_Feedback.xml"
I/O warning : failed to load external entity "/opt/cisco/anyconnect/CustomerExperienceFeedback/CustomerExperience_Feedback.xml"
I/O warning : failed to load external entity "/opt/cisco/anyconnect/CustomerExperienceFeedback/CustomerExperience_Feedback.xml"
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])

Tried

reinstall
https://unix.stackexchange.com/questions/532585/getting-dbind-warnings-about-registering-with-the-accessibility-bus
https://askubuntu.com/questions/1039243/packet-tracer-segmentation-fault-ubuntu-18-04
https://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect40/administration/guide/b_AnyConnect_Administrator_Guide_4-0/customize-localize-anyconnect.html
https://askubuntu.com/questions/1040485/unable-to-open-cisco-anyconnect-secure-mobility-client-on-my-ubuntu-18-04-lts

Solved

Delete with sudo /opt/cisco/anyconnect and install again.

DEV Community: Janko

test kodu

How to Fix GitHub Copilot Terminal Integration in VS Code

1. Enable Shell Integration

2. Relocate Chat for Stability

Summary for settings.json

Enhancing Todo Tree in VS Code

Automating DEV.to Publishing with GitHub Actions

What You Need

Creating a Reliable VS Code Task for New DEV.to Posts (Windows + PowerShell)

Problem

Launch Configuration

Key Principles

Working tasks.json

Task Behavior

Why It Works

Recommendations

Conclusion

Automating Git Workflow in VS Code: AI Commit & Sync with One Shortcut

Automating Git Workflow in VS Code: AI Commit & Sync with One Shortcut

Prerequisites

Step 1: Define the Macro in settings.json

Step 2: Map the Keyboard Shortcut

Step 3: Reload VS Code

How It Works

Notes

HTTrack Website Copier – Troubleshooting gzip Errors

VS Code Terminal Shell Integration (Windows)

Moved from https://jankoweb.tumblr.com/

Coronavirus stats: worldwide country position bookmarklet

Bookmarklet for hashtags insertion on social networks

Notes

Tested on

Inspired by

SOLVED: Cisco Anyconnect Linux Mint 20 SIGSEGV

Tried

Solved

Working `tasks.json`

Step 1: Define the Macro in `settings.json`