Support for Egyptian Hieroglyph Format Controls Unicode block

Description
Background
Egyptian hieroglyphs
The Egyptian hieroglyphs are not written linearly one character after the other horizontally or vertically; they are grouped in various spatial relations (most commonly signs vertically above signs, but other relations do occur).
Manuel de Codage
In order to represents Hieroglyphic texts in digital form various methods have been developed, of which the Manuel de Codage (MdC) became the de facto standard in the pre-Unicode era; it uses ASCII characters in combination with special characters such as : and * to represent hundreds of hieroglyphs and their complex positioning in relation to each other. The HieroTeX package for LaTeX takes MdC-encoded input and typesets hieroglyphs within a document.
Unicode
Hieroglyph support in Unicode was introduced in version 5.2 (2009). At the beginning there was no support for the non-linear structure of the text¹. This severely limited the usability of Unicode for Egyptology and linguistic description of the Egyptian language. Ten years letter, in Unicode 12.0 (2019) the Egyptian Hieroglyph Format Controls Unicode block was added, and quite recently in Unicode 15.0 (2022) is was expanded by 29 additional format controls. This makes at long last Unicode a capable standard for representing hieroglyph texts and fragments.
¹ Hangeul is also written non-linearly, but there thanks to the limited number of the basic characters that make the blocks and the predictable manner they are positioned, all the possible comminations for blocks that may occur in the Korean language are individually encoded. This cannot be done with hieroglyphs due to the sheer amount of basic signs and the complex ways they are positioned.
Typst support
I tried to typeset hieroglyphs in Typst with very limited success. See the code below (output) for the results. LuaLaTeX wasn’t helpful either, resulting in a slightly different kind of mess… However, it was LibreOffice (version <IP_ADDRESS> on Linux) that did produce impeccable output with the Egyptian Text font (see the attached image, cropped from a screenshot); the other fonts (NewGardiner, ‘Untitled1’², and two font that weren’t supposed to work because they don’t support the format controls: JSesh and Noto Sans EgyptHiero) produced faulty output as well.

² A supposedly ‘new’ version of NewGardiner named internally ‘Untitled1’…
#set page(
  width: auto,
  height: auto,
  margin: 0.5cm
)

#let test(font-name, url, ehfc)= {(
  table.cell[#link(url)[#font-name]],
  table.cell[#set text(font: (font-name), fallback: false); 𓌃𓂧𓏏𓏯𓀁𓏪𓆎𓅓𓊖 ],
  table.cell[#set text(font: (font-name), fallback: false); 𓄤𓆑𓂋],
  table.cell[#set text(font: (font-name), fallback: false); 𓆣𓂋𓇋𓁛],
  if ehfc {
    table.cell(align: center)[✅]
  }
)}

#table(
  columns: 5,
  stroke: none,
  table.hline(stroke: 0.08em),
  table.header(
    [Font name],
    [_mdw.t-km.t_\ ‘Egyptian language’],
    [_nfr_\ ‘fine, beautiful’],
    [_ḫprj_\ ‘Khepri’],
    [Has U+13430?]
  ),
  table.hline(stroke: 0.05em),
  ..test(
    "Egyptian Text",
    "https://github.com/microsoft/font-tools/tree/main/EgyptianOpenType/font",
    true
  ),
  ..test(
    "NewGardiner",
    "https://github.com/nederhof/opentypehiero/",
    true
  ),
  ..test(
    "Untitled1",
    "https://github.com/nederhof/opentypehiero/blob/master/tests/new.otf",
    true
  ),
  ..test(
    "JSesh font",
    "https://files.qenherkhopeshef.org/jsesh/JSeshFont.ttf",
    false
  ),
  ..test(
    "Noto Sans EgyptHiero",
    "https://notofonts.github.io/egyptian-hieroglyphs/",
    false
  ),
  table.hline(stroke: 0.08em),
)

What can be done? The Egyptian Text font has proved to work in LibreOffice, so I’d assume the problem is not in the font but in the rendering mechanisms of Typst and LuaLaTeX. I’m not familiar with Typst’s inner workings, but is this necessarily something complex to fix (that is, building the complex positioning and scaling system from scratch, implementing each of the format controls) or maybe it’s just something that has to be configured with the rendering mechanism? Notice that the word nfr with the font ‘Untitled1’ (third column, forth row in the table) is rendered… beautifully 🙂
For context, see HieroJax, which implements this in JavaScript.
For technical background, see the Wikipedia page on Egyptian Hieroglyph Format Controls and the Unicode documentation linked there.
Thank you from the bottom of my 𓄣𓏤 (heart ❤) for your time and effort!

When this problem is fixed, I intend to extend the capabilities of a Egyptological Typst package I work on to convert MdC input to Unicode, similarly to this (I see no reason to do that at the moment when its output is displayed wrong).
Use Case
Any scholarly work in Egyptology or linguistics that incorporates fragments of Egyptian hieroglyphs — in-line or as block examples — has to have support for typesetting hieroglyphs.

What can be done? The Egyptian Text font has proved to work in LibreOffice, so I’d assume the problem is not in the font but in the rendering mechanisms of Typst and LuaLaTeX. I’m not familiar with Typst’s inner workings, but is this necessarily something complex to fix (that is, building the complex positioning and scaling system from scratch, implementing each of the format controls) or maybe it’s just something that has to be configured with the rendering mechanism?

So, I think the relevant crate that we are using that is responsible for what you are trying to do is rustybuzz. It is responsible for text shaping, which basically means taking a sequence of Unicode codepoints and turning them into positioned glyphs from the respective font. I don't know the first thing about Egyptian hieroglyphs, but I don't assume that they are somehow a special case in comparison to other scripts, so that's most likely a relevant starting point. rustybuzz in turn is a Rust port of the harfbuzz library, which is pretty much the most widely used and best shaping engine out there (it's used in Chrome and many other programs). rustybuzz tries to always have the exact same output as harfbuzz, meaning that we should first check whether we get the same issues when shaping the provided texts with harfbuzz. If yes, that either means there is a bug in harfbuzz, or they simply haven't implemented it yet. If it does work there, then that might mean that there is some bug in rustybuzz.
But anyway, before diving deepter into this, I tried the Egyptian Text font locally, and this is what I get:

When I compare it to the screenshot you posted, it seems to look pretty similar. Could you specify what exactly is wrong in this output?

Oh, I just realized that you posted the output that you get.
Indeed, I get the same output when compiling with 0.11.1. But it works fine on main! The issue was most likely that, a couple of months ago, rustybuzz was many versions behind harfbuzz, which means that we also didn't have Unicode 15 support. By now, rustybuzz has luckily been synced back up, and we are currently using a newer version of rustybuzz. So this issue should be fixed by the next release. :)
Can you confirm that the following file corresponds to the exepected output? If so, I think we can close this issue.
typst.pdf

LuaLaTeX wasn’t helpful either, resulting in a slightly different kind of mess

You might need to enable HarfBuzz (Renderer=HarfBuzz fontspec option) as the default layout engine is probably not up to the task.

Oh, I just realized that you posted the output that you get.

Yeah, maybe I should’ve attached it as an image as well; the link to the PDF file doesn’t really stand out…

Indeed, I get the same output when compiling with 0.11.1. But it works fine on main! The issue was most likely that, a couple of months ago, rustybuzz was many versions behind harfbuzz, which means that we also didn't have Unicode 15 support. By now, rustybuzz has luckily been synced back up, and we are currently using a newer version of rustybuzz. So this issue should be fixed by the next release. :)

Woohoo! 🎉
Thank you; it makes me happy this is solved with no need to do anything extra in anyone’s part 🙂

Can you confirm that the following file corresponds to the exepected output? If so, I think we can close this issue. typst.pdf

Yes, I can confirm that. It took a while to compile Typst on my laptop, but now I have the main version installed and the output of Egyptian Text looks wonderful indeed. I guess in the case of NewGardiner the problem is with the font (it doesn’t work on any setup I’ve tried). The other fonts don’t support the Egyptian Hieroglyph Format Controls block, so they shouldn’t have worked at all and were added in the table for completeness (in order to show how it looks when the font lacks the relevant control characters).

@khaledhosny

You might need to enable HarfBuzz (Renderer=HarfBuzz fontspec option) as the default layout engine is probably not up to the task.

Thank you for the tip! 🙂
Tried to use HarfBuzz as the renderer like you said. It resulted with yet another kind of mess but now I suppose this is due to my TeX Live installation not having a recent enough version of HarfBuzz…
(It just amazes me how only now we are beginning to be able to write on a computer a language written in the one of the earliest scripts in human history, if not the first one)

@rwmpelstilzchen Would you happen to have some LaTeX source handy with your attempt to make this work there? I'd like to give it a shot myself (including being on a current version of TexLive & HarfBuzz) and post it to the hieroglyphs sample on polytype, especially if I can get it to work.
(Note the Typst sample generation there uses the current released version on Nixpkgs; as of this writing that is 0.11.1. I expect that sample to render nearly identical to the SILE sample when 0.12 comes out.)


Official Desktop GUI app

Please consider making an official GUI app for Ollama that runs on Windows, MacOS and Linux.
The official GUI app will install Ollama CLU and Ollama GUI
The GUI will allow you to do what can be done with the Ollama CLI which is mostly managing models and configuring Ollama. Essentially making Ollama GUI a user friendly settings app for Ollama.
Or even perhaps a desktop and mobile GUI app written in Dart/Flutter?
https://github.com/ollama/ollama/issues/2843

could me try ?
https://github.com/cogentcore/core/discussions/821

Hi there! check out some of these awesome Desktop (and/or Web) apps that run great with Ollama: https://github.com/ollama/ollama?tab=readme-ov-file#web--desktop


[Question] How to install this module for caddy

How to install this module for caddy
I am trying
caddy add-package https://github.com/dunglas/frankenphp/caddy

also

caddy add-package https://github.com/dunglas/frankenphp

Output:
Error: download failed: download failed: HTTP 400: https://github.com/dunglas/frankenphp/caddy is not a registered Caddy module package path (id=6229a763-4f7d-4658-90f6-758078b7b95b)

Currently, the easiest way is to follow these steps: https://github.com/dunglas/frankenphp/blob/main/docs/compile.md
Using xcaddy may also work if you correctly installed libphp locally.
We're are working with the Caddy team to allow using add-package, but it's not ready yet.


Use gardenlet priority class for gardenlet

How to categorize this PR?

/area control-plane
/kind bug
What this PR does / why we need it:
This PR switch the priority class for gardenlet from gardener-system-critical to gardenlet. Once gardener-system-critical  is cleaned from all the landscapes, we can switch back again to gardener-system-critical.
Which issue(s) this PR fixes:
Fixes https://github.com/gardener/gardener/issues/6422
Special notes for your reviewer:
Release note:

A bug causing `gardenlet` helm chart deployment to fail is fixed.

/cc @timebertt @kris94

/cherry-pick v1.52

/close


Reduce calls to Cipher.getInstance

I am going to revert some of the changes I made to AESCryptoService. I want to get the per-table crypto framework in first, and then we can make improvements to the implementation.

OK I'm going to take some of these improvements and open a separate PR against main so we can make improvements to the impl. Hopefully it won't conflict with the per-table changes too much.

The ProviderConfig.getProvider method is the synchronization point in the JVM code that I'm concerned about. We hit it with passwords, see: https://github.com/apache/accumulo/issues/2700#issuecomment-1131600304


dasharo-tools-suite: Add NovaCustom V54/56 and update image

@m-iwanicki still in draft? What are we missing?

@artur-rs it's ready for review


Call pattern formatting

Summary
This PR adds changes to delegate the formatting for match pattern nodes in the MatchCase formatting i.e., making the pattern.format calls. The implementation goes on to preserving the leading/trailing comments on the pattern nodes, parenthesizing if there are any such comments. If the node itself is parenthesized without any comments, the parentheses are preserved as is done in Black.
Test Plan
Added test cases for:

Pattern with parentheses, without leading or trailing comments
Pattern with parentheses, with trailing comments
Pattern with parentheses, with leading comments
Pattern with parentheses, with leading and trailing comments

Thank you

Lol, I can't approve the change

I'm so confused by this lol. Did Micha start this then Dhruv took over?

@MichaReiser I went ahead and implemented the "only trailing comments" and "no comments" part as well. I've added test cases and the output matches black.

I'm so confused by this lol. Did Micha start this then Dhruv took over?

Me and Micha discussed on Discord regarding calling the pattern.format() so that we can unlock https://github.com/astral-sh/ruff/issues/5834#issuecomment-1678848297 but that involved handling comments around the pattern. The implementation itself is similar to that of StmtWith formatting.

@dhruvmanila feel free to merge this when it's ready


CIA World Leaders site overhauled

CIA has redone their site. The current specified in the CIA World Leaders scraper config, https://www.cia.gov/library/publications/resources/world-leaders-1/index.html, returns a 404. The lists now reside at https://www.cia.gov/resources/world-leaders/foreign-governments/.

OK, this is a complete overhaul of the scraper, I guess. Are you up for giving it a shot, @ChrisjanWust?

OK, this is a complete overhaul of the scraper, I guess. Are you up for giving it a shot, @ChrisjanWust?


[Bug] blocks have no effective tool

Describe the bug
neither the quartz or smooth quartz elevator have effective tools and are thus not re-obtainable via mining them
To Reproduce
Steps to reproduce the behavior:

place an elevator
attempt to mine it
be sad

Expected behavior
elevators effective tool is a pickaxe, and they drop when they are mined
Environment

Minecraft: 1.17
Fabric Loader: 0.11.6
Fabric API: 0.35.2

Additional context
Blockus had the same issue with multiple blocks, and this is likely the same thing

Thank you for reporting, I was able to fixed this issue in version 1.2.3.
https://www.curseforge.com/minecraft/mc-mods/quartz-elevator/files


Please update dependency axios to to version 0.21.1 or later

Axios security alert:
https://github.com/advisories/GHSA-4w2v-q235-vp99

hi @notatestuser
Would it be possible to move forward with this pull request? https://github.com/binance-chain/javascript-sdk/pull/310/files
to update to 0.21.0, as it as been reported above is an axios vulnerability.
Cheers

Sure.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Simon @.>
Date: 6/28/21 9:44 AM (GMT-08:00)
To: binance-chain/javascript-sdk @.>
Cc: Peng Wang @.>, Author @.>
Subject: Re: [binance-chain/javascript-sdk] Please update dependency axios to to version 0.21.1 or later (#312)
hi @notatestuserhttps://github.com/notatestuser
Would it be possible to move forward with this pull request? https://github.com/binance-chain/javascript-sdk/pull/310/files
to update to 0.21.0, as it as been reported above is an axios vulnerability.
Cheers
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/binance-chain/javascript-sdk/issues/312#issuecomment-869839216, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE7MPSW34V6KHTBI44BABQDTVCRFFANCNFSM4YSHPMSA.


ddescribe and iit do not work

Somehow I cannot pick one test only anymore. Jest always scans for all tests and runs them all. Adding one ddescribe() in one of them has no impact.

I think you're looking for it.only() and describe.only()?

Yes, I tried these too. No effect. Probably broken?
Beware that I am running the tests through gulp-jest ...

Hmm, it works for me on master...what version are you using?
Just to be completely clear about what I'm seeing work for me:
describe('suit', function() {
  it.only('a', function() { console.log('a'); });
  it('b', function() { console.log('b'); });
});

(I only see 'a' printed with the above test)

Yes, that's what I am after and is not working here.
gulp-jest is using jest-cli version 0.4.0, see
https://github.com/Dakuan/gulp-jest/blob/master/package.json#L24
Can you try the above example of yours within gulp-jest?

My 2 cents: afaics it.only works, but in the related describe block (meaning if you have many test files they still run). What I would expect instead is that from all the test files, only the one marked as it.only is run.
PS: the repo looks quite dead (over 2 years ago) https://github.com/davemo/jasmine-only

Given that test files run in parallel, I don't think it'd be possible to know to skip other test files until it's too late. What you can do (and what I do often) is specify a unique part of the name of a test file as the first arg to the test runner. This will enure only tests matching that arg string get executed (and then internally, only the .only() test will run)

The classic workaround ;)

PS: the new jasmine syntax to run specific specs is to "focus" them with fit, fdescribe
http://jasmine.github.io/2.1/focused_specs.html
Not sure if it's possible to integrate it in jest though, not at least before upgrading to v2.0...
Refs https://github.com/facebook/jest/issues/74

@jeffmo sure, we all could do your classic workaround but let's think of DX and try to make our lives easier. I'd welcome a fit and fdescribe integration into jest. Really.

@binarykitchen: I don't think fit or fdescribe solve the problem here...and I don't see a solution, do you? How do you deal with the fact that tests run in parallel and therefore you can't know until you've already run all the tests whether one of them is marked as "focused" or "only"?

good point @jeffmo i am sure this problem has already been solved somewhere else with other unit test runners such as mocha. load and parse all files first and then decide which tests to run.

The karma runner for jasmine supports that. I don't know how it works exactly and how it differs from jest, still I think it's worth mentioning...
https://github.com/karma-runner/karma-jasmine

Any updates on supporting fit & fdescribe in jest?

Given that jest runs tests in parallel this seems quite impossible as @jeffmo pointed out earlier. What I've found to work well is it.only and passing the name of the test to jest, so it only runs a single file:
it.only(...) and jest MyTest.js

+1
By the way this seems quite possible, just the user would need to specify not to run the tests in parallel.

@danielstern you can now use -i -t <pattern> I guess.

For Node.js testing, just moved over to try Jest as opposed to my former go-to  test dependencies (Mocha, Chai, Proxyquire and Sinon) - the idea of consolidating to just having to use Jest was a primary motiviation, together with Mock by default behaviour... really liked the idea of cutting down on the test harness plumbing.  So far the experience using Jest has been really disappointing for reasons (one of many) such as this - too many workarounds and sub-optimal hacks to get equivalent behaviour that is expected to be out of the box. In fact, using Jest has resulted in more plumbing, not less - and less options / power. Using Mocha, Chai, Proxyquire and Sinon is not ideal either (hence the Jest trial).  Shame that a lot of the promise for Jest has not (yet) been realised - frustratingly close to what I was looking for - shall take another look in 6-12 months as I still think the library may one day get there.

@arcseldon what has disappointed you about Jest? Can you elaborate on that? It's crucial to get such feedback, so we can work on this to make Jest better.

@arcseldon this is a very vague comment on a random issue and isn't very helpful. If you have concerns or concrete issues and would like to see Jest improved, please help us by starting discussions in the appropriate places or send us pull requests to make Jest work for you.

I think it is possible. ava run test in parallel and it's test.only() is working as expected (only those tests are ran across all test files)

Here's a workaround I'm using
jest $(grep -rl '\\.only' test/unit)

FWIW ava has an issue for --only flag now. Maybe we should have the same?
https://github.com/avajs/ava/issues/1472


Question: how can I get the routeParams from inside the reducer?

I have a parametrized route. Depending on the parameter, I want to kick off an XHR that will fetch some document from the API.
As far as I understand, I'd have to listen for the LOCATION_CHANGE event inside some reducer and kick off another async action to fetch my document. However, the state does not include the routeParams, which means that I'd have to duplicate the route parsing code. How can I avoid this?
Or am I getting redux completely wrong here?

https://github.com/reactjs/react-router-redux#how-do-i-access-router-state-in-a-container-component


api docs: Document /realm/profile_fields api endpoint.

This documents the /realm/profile_fields endpoint.

@timabbott Can you have a look ?

@orientor This is ready for a review.

@akashaviator The custom profile fields will be a better in #/components/schemas as the same structure has been used multiple times, even in the /events /register PR.
For reference:
    CustomProfileField:
      type: object
      additionalProperties: false
      description: |
        Dictionary containing details of a single custom profile field.
      properties:
        id:
          type: integer
          description: |
            The id of the custom profile field.
        type:
          type: integer
          description: |
            The type of the custom profile field.
        order:
          type: integer
          description: |
            The order of the custom profile field.
        name:
          type: string
          description: |
            The name of the custom profile field.
        hint:
          type: string
          description: |
            A hint regarding the custom profile field.
            For example, 'What are you known for?'.
        field_data:
          type: string
          description: |
            The data related to the custom profile field.
```yaml

Your version is definitely more descriptive, so once you relocate it I will change my version accordingly. I think that should avoid any merge conflicts.

@akashaviator The CustomProfileField part has been merged so after rebasing you can directly use it.

@orientor This is ready for a second review.

@akashaviator I should have mentioned this earlier but your descriptions are better and more descriptive than the current CustomProfileField definitions. So I think it would be better if you edited the CustomProfileField schema to add your descriptions. I think that after this and the JsonSuccess change which I had missed before this PR should be ready for merging.

@timabbott This seems ready to be merged.

Merged as the series ending with 2095ed6ae7a7ed2123b88f6108553a20092e98c2, after adding my own commit editing a lot of the text.  Thanks @akashaviator!
I think ideally we'd deduplicate the descriptions of fields like hint in a CustomProfileFieldBase type?


Option "css.autoInsertVendorPrefixes" doesn't work

I created the preferences.json file and put it in ~/emmet directory. But nothing has changed.
df  and d:f still expand with vendor-prefixes.

Atom: version 1.4.0
Emmet-atom: version: 2.3.17
System: Ubuntu 14.04

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29877321-option-css-autoinsertvendorprefixes-doesn-t-work?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).

https://github.com/emmetio/emmet-atom#extensions-support

By default, it’s ~/emmet, e.g. emmet folder in your system HOME folder.


Develop

new class HDF5Helper for easier file output
improved memory as well as performance in createMatrix by using dynamic arrays and removing unnecessary recreation of objects

I didn't find any reference to the version of boost that is downloaded automatically in the readme. There is an example if one wants to download and compile it oneself where 1.76 is mentioned, but this number needs to be adjusted to the version that one downloads anyway.

I didn't find any reference to the version of boost that is downloaded automatically in the readme. There is an example if one wants to download and compile it oneself where 1.76 is mentioned, but this number needs to be adjusted to the version that one downloads anyway.

You're right, my bad. It's alright as it is.


Add Screentop support LeapC 4.9.2

Screentop tracking mode added (the view will be identical to Desktop though)
Replace the setPolicy(HMD) by the Tracking Mode setters.
Updated the LeapC.dll from LeapDeveloperKit_4.9.2+52299_win

NB : even if HMD/Screentop policies are still there they should not be used anymore!

I have tested this locally and it looks good.


Bug: Date fields with empty values throwing errors

Hi! I think there may be a bug in the API. Everything ultimately works as expected, but I noticed a lag when I created a dataview query that also called the metadata menu API. The console revealed a hint:
plugin:metadata-menu:7544 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'path')
    at DateField.validateValue (plugin:metadata-menu:7544:56)
    at FieldInfo.setInfos (plugin:metadata-menu:8909:37)
    at eval (plugin:metadata-menu:8984:27)
    at Generator.next (<anonymous>)
    at eval (plugin:metadata-menu:72:61)
    at new Promise (<anonymous>)
    at __async (plugin:metadata-menu:56:10)
    at eval (plugin:metadata-menu:8979:44)
    at Array.forEach (<anonymous>)
    at fileFields (plugin:metadata-menu:8979:27)

I have a "completed" date field on files tagged #task that I'm querying, but it's expected to be empty whenever it's a task I'm still working on. This date field is set up as a link to a daily note file in format [[2022-10-07]]. I'm trying to use a custom script calling Metadata Menu's API in order to update that field programmatically, but it's throwing the above error every time the file renders and the referenced "completed" field is empty.
This is the line of code that seems to be generating the error:
await mm.fileFields(page.file.path)

If I put a proper value in "completed," the error doesn't appear. Is it possible Metadata Menu isn't set up to handle empty fields? Is there some other way I can handle empty fields gracefully?
Expected behavior might be that when it sees a date field set up to accept daily note file links, and it sees an empty field, it does NOT attempt to traverse the file path. But maybe I'm misunderstanding the error. If so, any guidance appreciated!

good catch! this is fixed in 0.2.10: empty date field are considered as valid now


Benchmarks sometimes get stuck

I unfortunately don't have a reproducible example, as this doesn't happen deterministically, but sometimes the benchmarks seem to get stuck. Restarting the benchmarks usually fixes the problem.

And no suggestions to set -t100in stderr? You might try setting debug build flag.

Eventually, I get
This benchmark takes more than 100 seconds. Consider setting --timeout, if this is unexpected (or to silence this warning).

Is this to be expected? The benchmarks shouldn't vary too much and when rerunning, it doesn't occur, so this feels like some bug.

This is expected, either set --timeout 100, or alternatively increase --stdev.


which data is selected/not selected in the chart.js graphs should be in the permalink url

followup on #108
use case: drop the Max and p99.9 from view, or drop QPS after verifying it's flat, etc...

another thing missing is the search filter part


AddDependency.onlyIfUsing does not work as advertised

The description for AddDependency.onlyIfUsing states:
"Add the dependency only if using one of the supplied types. Types should be identified by fully qualified class name or a glob expression"
There are two major inaccuracies in this description.
1 - Glob expressions are not supported, only a literal fully qualified name is accepted.
Note the lack of glob support in this snippet from AddDependencyVisitor where onlyIfUsing is implemented:
        if (onlyIfUsing != null) {
            Set<JavaType> found = ctx.getMessage(JavaType.FOUND_TYPE_CONTEXT_KEY, emptySet());
            if (onlyIfUsing.stream().noneMatch(t -> found.contains(JavaType.Class.build(t)))) {
                return maven;
            }
        }

Only being contained in that set on the ExecutionContext counts as being "used", which no glob pattern ever will be.
2 - The type wont be found unless some other recipe has found the type and added a specific entry into the ExecutionContext. The only visitors which will currently add this key to the execution context are FindMethods, FindTypes or AddImport.

Fixed by: #432


Index out of range: no indices are valid: 0

Unhandled exception:
RangeError (index): Index out of range: no indices are valid: 0
#0      Iterable.elementAt (dart:core/iterable.dart:648:5)
#1      _getMainActivityJavaPath (package:flutter_native_splash/android.dart:335:27)

#2      _javaOrKotlin (package:flutter_native_splash/android.dart:307:36)

#3      _applyMainActivityUpdate (package:flutter_native_splash/android.dart:288:33)

#4      createSplash (package:flutter_native_splash/android.dart:39:9)

#5      createSplash (package:flutter_native_splash/flutter_native_splash.dart:20:11)

#6      main (file:///C:/Flutter/.pub-cache/hosted/pub.dartlang.org/flutter_native_splash-0.1.8+3/bin/create.dart:5:3)
#7      _startIsolate. (dart:isolate-patch/isolate_patch.dart:303:32)
#8      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)
pub finished with exit code 255
App is Kotlin.

AndroidManifest.xml:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="br.art.code.meucronogramacapilar"
    xmlns:tools="http://schemas.android.com/tools">
    <application tools:replace="android:label,android:icon" android:name="io.flutter.app.FlutterApplication"
        android:label="Meu Cronograma Capilar" android:icon="@mipmap/ic_launcher" android:roundIcon="@mipmap/ic_launcher_round"
        android:fullBackupContent="@xml/backup_rules">
        <receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationBootReceiver">
            <intent-filter>
                <action android:name="android.intent.action.BOOT_COMPLETED"></action>
            </intent-filter>
        </receiver>

        <receiver android:name="com.dexterous.flutterlocalnotifications.ScheduledNotificationReceiver" />

        <meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id"/>
        <meta-data android:name="com.google.android.gms.ads.APPLICATION_ID" android:value="ca-app-pub-xxxxxx"/>

        <activity android:name="com.yalantis.ucrop.UCropActivity" android:screenOrientation="portrait"
<EMAIL_ADDRESS>
        <activity android:name="com.facebook.FacebookActivity" android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation"
            android:label="@string/app_name" />

        <activity android:name="com.facebook.CustomTabActivity" android:exported="true">
            <intent-filter>
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
                <data android:scheme="@string/fb_login_protocol_scheme" />
            </intent-filter>
        </activity>

        <activity android:name=".MainActivity" android:launchMode="singleTop" android:theme="@style/LaunchTheme"
            android:configChanges="orientation|keyboardHidden|keyboard|screenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
            android:hardwareAccelerated="true" android:windowSoftInputMode="adjustResize">
            <meta-data android:name="io.flutter.app.android.SplashScreenUntilFirstFrame" android:value="true" />
            <intent-filter>
                <action android:name="android.intent.action.MAIN"/>
                <category android:name="android.intent.category.LAUNCHER"/>
            </intent-filter>
        </activity>
    </application>

    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
</manifest>

Thanks for reporting!
Regex couldn't find package tag on AndroidManifest.xml because package is not the last tag as in default projects.
This is now fixed in 0.1.8+4. Please update the package and run again.
dev_dependencies:
  flutter_native_splash: ^0.1.8+4

Thank you, @henriquearthur, but there is a lot of issues in this plugin that prevents me from using it =\
The most pressing issue is the image dimension's. I have a OnePlus 6 (1080x2280, 19:9, 402ppi) and a MotoG 1st Edition (720x1280, 16:9, 326ppi). In the OnePlus, my splash is too small. In MotoG, the splash barely fits on the screen.
I was hopping a plugin to automatically make my splash screen be, more or less, the same in different screen dimensions/resolutions =\

Indeed image sizing is something this package needs to do better and consistently.  Right now it only uses dpi variants on Android and @2x @3x on iOS.
There is a issue for tracking image size and position features (https://github.com/henriquearthur/flutter_native_splash/issues/11). I will try to address it soon.

Also, would be nice to write down in the docs which size the image template must be.

That's part of the problem, there is no specific size. Android devices vary from low, medium and high resolutions and we should support all sizes.
If the given image is too large (in resolution) it will look good in high res devices and not so good in low res. If the image is too small, it will be good in low res and not so good in high res.
I need to do more tests with different screen sizes as well.


Export Button

example output

cleaned output
can't remove [object Object], it's the actual rectangle that's used for everything, if that is removed then functionality is lost

ignore "swag"...


Change in Dynatrace metrics Documentation - new feature release

Learn Build status updates of commit 39c4d40:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/partner-solutions/dynatrace/dynatrace-create.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-how-to-manage.md
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-1.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-2.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-3.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-UI.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-metrics-and-logs.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-how-to-manage/dynatrace-metrics-and-logs-updated.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/dynatrace-create.md

Line 70, Column 5: [Warning: file-not-found - See documentation] Invalid file link: 'media/dynatrace-create/dynatrace-metrics-and-logs-checkbox.png'.
Line 89, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 103, Column 238: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 103, Column 238: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' will be broken in isolated environments. Replace with a relative link.

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md

Line 51, Column 161: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51, Column 161: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 9065167:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/partner-solutions/dynatrace/dynatrace-create.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-how-to-manage.md
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-1.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-2.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-3.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-UI.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-metrics-and-logs.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-how-to-manage/dynatrace-metrics-and-logs-updated.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/dynatrace-create.md

Line 89, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 103, Column 238: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 103, Column 238: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' will be broken in isolated environments. Replace with a relative link.

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md

Line 51, Column 161: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51, Column 161: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 5de5cd0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/partner-solutions/dynatrace/dynatrace-create.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md
:warning:Warning

Details

articles/partner-solutions/dynatrace/dynatrace-how-to-manage.md
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-1.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-2.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-guide-3.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-contributor-UI.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-create/dynatrace-metrics-and-logs.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/media/dynatrace-how-to-manage/dynatrace-metrics-and-logs-updated.png
:white_check_mark:Succeeded

articles/partner-solutions/dynatrace/dynatrace-create.md

Line 89, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 103, Column 238: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 103, Column 238: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-activity-logs-azure-monitor' will be broken in isolated environments. Replace with a relative link.

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md

Line 51, Column 161: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51, Column 161: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/partner-solutions/dynatrace/dynatrace-create' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@vpriyanshi
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
We'll close this PR. Thank you.


fix(table): pass id OR tableId to TableBody to fix snapshots

Closes #1538
Summary

Recent PR changed how tableId is passed to Table's children components. All components were receiving the prop as tableId={id || tableId}, but TableBodyRow was receiving it as tableId={id}. If id was not set by the user, null was displayed in the child  element

Change List (commits, features, bugs, etc)

Change TableBodyRow prop to tableId={id || tableId}
Change 1 story to not pass an id so that this use-case can be tested in the future

Acceptance Test (how to verify the PR)

See that the snapshot updated to the default tableId (we are already passing id to all other tables so we weren't able to see this bug)

:tada: This PR is included in version 2.112.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support for vertical tabs

Add a big boost in developer productivity by adding support for vertical tabs for files. This is a basic feature in most browsers and is requested by many users.
Tabs are one of the most used features in VSCode in my opinion and improving them has a direct and strong impact in productivity. It would allow for many more tabs to be opened at the same time, without having to scroll them all the time, and could open up possibilities like grouping or archiving in the future.
Duplicates of this issue (that were closed for some reason) have 57 upvotes combined:
25 upvotes: https://github.com/microsoft/vscode/issues/75749
28 upvotes: https://github.com/microsoft/vscode/issues/85527
4 upvotes: https://github.com/microsoft/vscode/issues/65193
The following extension has almost 10,000 installs, but it requires a hack to work (I couldn't do it):
https://marketplace.visualstudio.com/items?itemName=pzuraq.vertical-tab-bar

While I'm working on this with my own, here's my idea how it should be implemented.

If verticalTabs option is introduced, there're 6 combinations editor should consider.

Tabs (true) Breadcrumbs (true) Vertical Tabs (true)

┌─────────────────────────┐
│Title + Breadcrumbs      │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

Tabs (true) Breadcrumbs (true) Vertical Tabs (false)

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (true) Breadcrumbs (false) Vertical Tabs (true)

┌─────────────────────────┐
│Title                    │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

Tabs (true) Breadcrumbs (false) Vertical Tabs (false)

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (false) Breadcrumbs (true) Vertical Tabs (false)

┌─────────────────────────┐
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (false) Breadcrumbs (false) Vertical Tabs (false)

┌─────────────────────────┐
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Discuss should be made how layout will be laid on these combinations.
Plus, referring to the source code, since Title (with breadcrumbs) and Tabs are tightly glued together, we need to detach them gently.

I think that looks great.
Two more ideas:

To have the option to have the vertical tabs as a panel like the File Explorer and the Outline panels. That way we can have the files and the opened tabs in the same column and save a lot of space. The file explorer and the tabs both represent a similar type of information if you think about it: the File Explorer shows files in general as they are in the hard drive and the tabs which files are opened, arranged by users' preference.

When splitting the editor, to be able to configure vertical tabs or horizontal tabs in each section separately.

To have the option to have the vertical tabs as a panel like the File Explorer and the Outline panels. That way we can have the files and the opened tabs in the same column and save a lot of space. The File Explorer and the tabs both represent a similar type of information if you think about it: the File Explorer shows files in general as they are in the hard drive and the tabs which files are opened, arranged by users' preference.

I think VSCode already has it although it's a global one, not a per-editor-group.

I don't have that option here. How do you activate it? I have Folders, Outline, Timeline, NPM Scripts in the Explorer panel.

Simply right click on any list header will show context menu for toggling it.

Maybe it's an extension you have?

Weird. It's a built-in functionality since many years ago.

@santiagopuentep maybe you have previously moved Open Editors onto the Output Panel. Does it appear as a tab there? Or in the context menu of any tab there?

@gjsjohnmurray I searched everywhere but it's nowhere to be found. Two of my colleagues do have it so it'll remain a mystery I suppose. Thanks for the help anyway.

Found it. "explorer.openEditors.visible": 1 solved the problem.

@orange4glace From what I can see the Open Editors panel work almost exactly like vertical tabs.
The only problem I see is that it's not visible when other panels are opened (like search). So maybe improving panels to to be able to place them on a new column (for example a column with all the panels and one with the Opened Editors panel) or to the other side of the screen (to have some to the right and some to the left) I think could be a great way to solve vertical tabs + adding new possibilities for the other panels too.

@orange4glace Also, moving the close button to the right and removing the full path would make them look exactly like tabs and would remove a lot of noise to the panel.

Found it. "explorer.openEditors.visible": 1 solved the problem.

You may want to set that larger than 1. Default value is 9.
Helptext for the section doesn't state that a value of zero disables the panel entirely. It probably ought to.

I would love for VSCode to have official support for vertical tabs. I found the now discontinued VS extension "custom document well" to be a really big productivity boost so I made a clone of it. The extension API in VSCode didn't permit me to do most of the things I wanted so it's sadly not a normal extension.
I don't want to be doing self promotion so no link. But some ideas.
I handled the issue of a split document well by splitting the vertical tabs. It also supports grouping and coloring per group.

Since that screen shot was taken I've also added pinning, which keeps the pinned tab at the top.

Visual Studio now has vertical tabs.
Make it happen!
Specifically tabs on the right.

Visual Studio now has vertical tabs.
Make it happen!
Specifically tabs on the right.

How can it be enabled?

Visual Studio now has vertical tabs.
Make it happen!
Specifically tabs on the right.

How can it be enabled?

How can it be enabled?

https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-v16.4#vertdoctabs

How can it be enabled?

https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-v16.4#vertdoctabs

enable workbench.files.action.focusOpenEditorsView
it will constantly stay visible in top left corner and will not scroll with project files which is good
for fast switching trough opened files: command + option + left/right

虽然我正在用自己的方式解决这个问题，但这是我应该如何实施它的想法。

如果verticalTabs引入选项，编辑器应该考虑 6 种组合。

标签_(true)面包屑(true)垂直标签(true)_

┌─────────────────────────┐
│Title + Breadcrumbs      │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

标签_(true)面包屑(true)垂直标签(false)_

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

标签_(true)面包屑(false)垂直标签(true)_

┌─────────────────────────┐
│Title                    │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

标签_(true)面包屑(false)垂直标签(false)_

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

标签_(false)面包屑(true)垂直标签(false)_

┌─────────────────────────┐
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

标签_(false)面包屑(false)垂直标签(false)_

┌─────────────────────────┐
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

应该讨论如何在这些组合上进行布局。
另外，参考源代码，由于_Title（带面包屑）_和_Tabs_紧密地粘在一起，我们需要轻轻地将它们分开。

While I'm working on this with my own, here's my idea how it should be implemented.

If verticalTabs option is introduced, there're 6 combinations editor should consider.

Tabs (true) Breadcrumbs (true) Vertical Tabs (true)

┌─────────────────────────┐
│Title + Breadcrumbs      │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

Tabs (true) Breadcrumbs (true) Vertical Tabs (false)

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (true) Breadcrumbs (false) Vertical Tabs (true)

┌─────────────────────────┐
│Title                    │
├──────┬──────────────────┤
│Tabs  │Editor space      │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
│      │                  │
└──────┴──────────────────┘

Tabs (true) Breadcrumbs (false) Vertical Tabs (false)

┌─────────────────────────┐
│Tabs                     │
├─────────────────────────┤
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (false) Breadcrumbs (true) Vertical Tabs (false)

┌─────────────────────────┐
│Title + Breadcrumbs      │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Tabs (false) Breadcrumbs (false) Vertical Tabs (false)

┌─────────────────────────┐
│Title                    │
├─────────────────────────┤
│Editor space             │
│                         │
│                         │
│                         │
│                         │
│                         │
└─────────────────────────┘

Discuss should be made how layout will be laid on these combinations.
Plus, referring to the source code, since Title (with breadcrumbs) and Tabs are tightly glued together, we need to detach them gently.

Wow!! amazing !
Can you write an article to guide me and let me experience it ?

I want vertical tabs for open editors to be implemented the ways edge does for browser tabs
https://user-images.githubusercontent.com/32778608/126530941-6f93e69a-f995-46d8-84fc-968e8d2f07b2.mp4

The best implementation of vertical tabs I saw is in WebStorm (IntelliJ IDEA):

This is the only reason I still using WebStorm instead of VS Code 💁♂

Yep, IDEA IDEs get this perfectly right - especially in terms of being configurable, for left or right positions and alignment, and the option to keep tabs sorted or grouped, or manually sortable with drag-and-drop.
The "Open Files" panel doesn't cut it, because it doesn't stay on-screen - leaving no obvious way to switch between tabs when you have another panel open. (unless you also leave the tabs enabled - which, if you have to reach for two different UIs to navigate between tabs at different times, that really doesn't work either.)
And the vertical-tab-bar extension is just a CSS styling of "OpenFiles", with all the same problems.
The bot said it was added almost a year ago, but I don't think we got any confirmation from a human?
Can the devs please post an update? Where/is this on the roadmap?

Yep, IDEA IDEs get this perfectly right - especially in terms of being configurable, for left or right positions and alignment, and the option to keep tabs sorted or grouped, or manually sortable with drag-and-drop.
The "Open Files" panel doesn't cut it, because it doesn't stay on-screen - leaving no obvious way to switch between tabs when you have another panel open. (unless you also leave the tabs enabled - which, if you have to reach for two different UIs to navigate between tabs at different times, that really doesn't work either.)
And the vertical-tab-bar extension is just a CSS styling of "OpenFiles", with all the same problems.
The bot said it was added almost a year ago, but I don't think we got any confirmation from a human?
Can the devs please post an update? Where/is this on the roadmap?

Haha ,
the bot mean that this task is going into the vscode team's work,
but we don't know when the vscode team will be finished.

I hope vscode team can take reference from the awesome work done by ms edge team. The vertical tabs, tab groups, and collections in ms edge is really nice. I switched to edge and stayed with edge for that reason

Please advise which code editor has convenient vertical tabs?

Please advise which code editor has convenient vertical tabs?

JetBrains IDEs are cool in that perspective. E.g. WebStorm.

Open Editors can now be pinned on the side since 1.64 (January 2022).

Is the issue closed or is there any important missing feature in Open Editors right now ?

@pilatte the open editor's position wasn't the feature request. Folks are requesting the ability to place the tabs vertically in a column on either side of the editor.
A question for the VS Code devs - What's the technical hurdle for implementing this feature?

You can have the list of opened tabs on the left if you have the side bar on the right, you just can't have both on the same side.
@the0neWhoKnocks I agree that Opened Editors is a list of opened tabs and not a proper vertical tab bar.

Yep, IDEA IDEs get this perfectly right - especially in terms of being configurable, for left or right positions and alignment, and the option to keep tabs sorted or grouped, or manually sortable with drag-and-drop.
The "Open Files" panel doesn't cut it, because it doesn't stay on-screen - leaving no obvious way to switch between tabs when you have another panel open. (unless you also leave the tabs enabled - which, if you have to reach for two different UIs to navigate between tabs at different times, that really doesn't work either.)
And the vertical-tab-bar extension is just a CSS styling of "OpenFiles", with all the same problems.
The bot said it was added almost a year ago, but I don't think we got any confirmation from a human?
Can the devs please post an update? Where/is this on the roadmap?

To add to this comment, there is a clearer, more User friendly visual language implemented with tabs:

A Tab is a UI that is linked to an area currently being viewed.
The current tab stands out more than it's siblings (Browsers slightly grey out siblings, Editors add an indicator like a highlight line), and the font generally stands out more.
Users can easily position/order a Tab based on their preference/need.
Since the tabs are linked to the Editor, there's a visual grouping especially when you've split the views.
Having a close button gives a User an exit, when they're not familiar with keyboard shortcuts.

To be fair:

[x] being configurable, for left or right positions [Kinda]
[x] manually sortable with drag-and-drop [You can reorder them however you like]
[x] it doesn't stay on-screen [it does if you put it in the side panel opposite to side bar]
[x] A Tab is a UI that is linked to an area currently being viewed. [It is clickable]
[x] The current tab stands out more than it's siblings [It does]
[x] Users can easily position/order a Tab based on their preference/need [You can order them however you like]
[x] Since the tabs are linked to the Editor, there's a visual grouping especially when you've split the views [they are grouped]
[x] Having a close button gives a User an exit, when they're not familiar with keyboard shortcuts [There is a cross]

@pilatte

I'm aware of Open Editors capabilities, and have implemented custom styling in the past to get it closer to vertical tabs as I could, but it was still clunky since I had to use the Custom CSS and JS Loader plugin to do so.
My previous comment was in regards to Tabs as a UI and visual language. Tabs are visually linked to editor groupings, and generally easier to cognitively and visually navigate.
Tabs are present on initial load of the App (unlike Open Editors which takes some hunting if one is not familiar).
The "grouping" of editors is fine if the view is split once, but when split multiple times mixed with horizontal and vertical splits can be confusing since the group names aren't displayed anywhere and can be even more confusing if you have the same tab split since you just have a bunch of "group #" with the same file name listed. Where as with Tabs, the "linking" I was referring to was not functionally, but visually.

At the end of the day, it's about preference. Personally I prefer tabs (for the reasons I and others have outlined), and if folks prefer to use Open Editors, more power to them. That said, this is a feature request ticket for vertical tabs and any further discussion should remain on that topic.
If I took my car into a mechanic to get it fixed and they replied with "why fix the car, how about you just take the bus instead", sure that's an option, but it is not what's being requested.

I would also prefer true vertical tabs, I was just pointing out that most of the feature listed have already been looked into by VSCode devs when they did the Open Editors. I didn't know if you knew all the feature packed into Open Editors which might be a suitable alternative for people in the mean time until vertical tabs become available.

Why is so difficult to add true vertical tabs? I really can't understand.

I usually work with the open editors, explorer, find, etc. collapsed. Only expanding them when I need to do a global search or walk the tree in the file explorer. Unfortunately I can’t have everything collapsed on the right AND a non-collapsed open editors list.
Typically I also work with 10+ tabs open to switch between different levels and parts of a system. I also typically lose tabs amongst the multiple rows of tabs at the top.
Having a vertical list of tabs would solve this for me.

Why is so difficult to add true vertical tabs? I really can't understand.

The layout in there is quite complicated, and the Tabs are currently very bound to the Editor area, so extracting them is quite painful, as a complete refactor of the layout would be needed, also there are other components IN the tabs which would need to be extracted to a separate section of the layout. I imagine that is the main reason it's not yet done.

Open Editors can now be pinned on the side since 1.64 (January 2022).

Is the issue closed or is there any important missing feature in Open Editors right now ?

Vertical tabs like this, you can take some help from the team at edge
https://github.com/microsoft/vscode/issues/108264#issuecomment-884353123

Why is so difficult to add true vertical tabs? I really can't understand.

The layout in there is quite complicated, and the Tabs are currently very bound to the Editor area, so extracting them is quite painful, as a complete refactor of the layout would be needed

Several people did this already, with < 1 page of CSS. No reason VS Code couldn't start there, and think about refactoring later.

Since we have the Open Editors now, and if we agree they are functionally equivalent to vertical tabs, what we need may be an option to "display as vertical tabs", e.g. change the styling and mount it on the left side of the editor view.
Is that possible, or is there another missing feature, in terms of being able to add side panels to the sides of the editor view?

Why is so difficult to add true vertical tabs? I really can't understand.

The layout in there is quite complicated, and the Tabs are currently very bound to the Editor area, so extracting them is quite painful, as a complete refactor of the layout would be needed

Several people did this already, with < 1 page of CSS. No reason VS Code couldn't start there, and think about refactoring later.

Can you link to me to code, I'd like to implement this locally to try it

@pilatte chekcout this repo https://github.com/cmmdmx/vscode-vertical-tabs , its possible and with some more polish it can be production ready

@anoushk1234 still requires the "Custom CSS and JS" plugin though, yeah? (looks promising though.)

I managed to get vertical tabs to function in a way that I'm happy with by using the built-in functionality that VS Code already offers. What I did was click the menu and enable "Open editors" as others have mentioned, but then I also went into my settings and unchecked the box that says, "Show Tabs". Now I can see all of my open tabs on the side and the name of the file that I am in at the top.
Enable Open Editors

Disable Show Tabs in settings

Now I have vertical tabs

@DRD161 these aren't vertical tabs - scroll back through the thread, where this option has been suggested and rejected repeatedly.

is there any news?

what if we just fork it and add it ourselves?

I'd like to ask what the status on this. It has been almost 2 years since it was suggested...

What's the difference between what you're looking for and what I posted above @ManuGraiph?

@LukeTowers I'll answer your question: it's not an official tool, there should be a flag or something in the vscode settings

Meh, that's probably why there hasn't been any progress on it. Anyone who actually cares enough will just make the 4 required settings changes and then move on to more important things.

@LukeTowers That's how i use vs code, but it's not the same, one thing is tabs on the side, another is the open editors. Im just asking what's the status of it.

There is one thing that prevents using Open Editors as a vertical tabs: a single click does not transfer focus to the editor. It is very uncomfortable.

what is the status of this? Still in backlog? Already in progress? Postponed? Deprecated? It was about 2 years ago since was mentioned added to backlog.

Commenting to keep this alive.  This would greatly enhance the VS Code experience!  👍

It is recommended to learn the vertical tabs and tab grouping of edge, which is really a productivity tool.

how is this not done yet?

If it would be possible to upvote for this one again, I would do that.

Commenting to keep this alive². I'd love vertical tab.

The absence of Vertical tabs is still a show-stopper for me

The editor is great.
Reducing the screen height by another 2-4 tab rows on a laptop makes it really hard to use. An integration like in intellij's phpstorm is highly requested.
Keep up the good work with the editor! Its such a good product for beeing free <3

It looks like they scored on the feature, it's a pity, it's very lacking

Bump!

At least make a dropdown of all tabs, without anything else in it.

@bpasero As mentioned in https://github.com/microsoft/vscode/issues/155012#issuecomment-1191199162, is this now being assessed?

Just as a note to everyone requesting this feature for 2+ years now - not only it is possible to do this, I've already done it as an extension (kind of). Along with other features like regexps for tab titles and more.
Here's the problem though - while it works well enough for me:

it's hard to set up and not documented
it's all or nothing for my needs, and not easily customizable
still misses some work to be user-friendlier.

Unfortunately, I don't use VS Code (part of the reason being vertical tabs, but there are others), and I've sunk way too much time into this already, with probably weeks of effort left.
I don't have that much spare time for this, and as I don't use VS Code, I'm not exactly inclined to forgo my next vacation for this.
That leaves me with basically three options:

I just put it on GH and hope someone else can make sense of it and finish it.
I make it a paid addon (something symbolic, like $3 or $5 - I know VS code is free, but I'm not exactly Microsoft), and make sure it stays functional and supported along with VS Code updates.
Just roll the dice, finish it and rely on individual donations. Which, seeing how even some really large corporations have problems supporting open-source that makes them billions, makes me question if it isn't just a futile proposition, for such a niche project (even though with a big productivity win for people that need it).

Opinions?

Opensource it. But it's going to be a mess, and won't work reliably as a plugin. I had a look at the vscode interface code — it's simply not designed with the ability to implement vertical tabs. That's why no one is saying it will be done at all. The estimate is too big.On 2022-12-24, at 20:25, vlascik @.***> wrote:
Just as a note to everyone requesting this feature for 2+ years now - not only it is possible to do this, I've already done it as an extension (kind of). Along with other features like regexps for tab titles and more.
Here's the problem though - while it works well enough for me:
it's hard to set up and not documented
it's all or nothing for my needs, and not easily customizable
still misses some work to be user-friendlier.
Unfortunately, I don't use VS Code (part of the reason being vertical tabs, but there are others), and I've sunk way too much time into this already, with probably weeks of effort left.
I don't have that much spare time for this, and as I don't use VS Code, I'm not exactly inclined to forgo my next vacation for this.
That leaves me with basically three options:
I just put it on GH and hope someone else can make sense of it and finish it.
I make it a paid addon (something symbolic, like $3 or $5 - I know VS code is free, but I'm not exactly Microsoft), and make sure it stays functional and supported along with VS Code updates.
Just roll the dice, finish it and rely on individual donations. Which, seeing how even some really large corporations have problems supporting open-source that makes them billions, makes me question if it isn't just a futile proposition, for such a niche project (even though with a big productivity win for people that need it).
Opinions?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Just as a note to everyone requesting this feature for 2+ years now - not only it is possible to do this, I've already done it as an extension (kind of). Along with other features like regexps for tab titles and more.
Here's the problem though - while it works well enough for me:

it's hard to set up and not documented
it's all or nothing for my needs, and not easily customizable
still misses some work to be user-friendlier.

Unfortunately, I don't use VS Code (part of the reason being vertical tabs, but there are others), and I've sunk way too much time into this already, with probably weeks of effort left.
I don't have that much spare time for this, and as I don't use VS Code, I'm not exactly inclined to forgo my next vacation for this.
That leaves me with basically three options:

I just put it on GH and hope someone else can make sense of it and finish it.
I make it a paid addon (something symbolic, like $3 or $5 - I know VS code is free, but I'm not exactly Microsoft), and make sure it stays functional and supported along with VS Code updates.
Just roll the dice, finish it and rely on individual donations. Which, seeing how even some really large corporations have problems supporting open-source that makes them billions, makes me question if it isn't just a futile proposition, for such a niche project (even though with a big productivity win for people that need it).

Opinions?

Live your life and don't think about this missing feature for the time being. As they mentioned, the feature request will go through another voting stage next year and hopefully we (the public) can get it pushed through this time.

I just started at a new company. They are hiring a few people and the only current dev is using PHPStorm just like me at my last job. We were very close to switch to VSCode because it is getting more popular in our community. It is funny to think that such a simple feature had a good impact in our decision. We are now going to use PHPStorm!

I currently have 21 tabs open and it's impossible to work efficiently with current tabs UI:

I spend way too much time looking for a particular tab at this point

IMO, the best solution would be:

Implement hierarchical (grouped) and colored tabs like Chrome has:
Implement ability to set custom favicon for each tab. (This probably sounds weird to you but it's actually a great idea IMO despite being weird.)
Implement vertical tabs option.

These extensions have various forms of manual drag and drop and coloring and grouping functionality but they are not ideal because they require a separate sidebar panel and they lack integration with tabs bar:

https://marketplace.visualstudio.com/items?itemName=DeepakPahawa.flowbookmark
https://marketplace.visualstudio.com/items?itemName=kdcro101.favorites

Guys, I think that this tutorial solves part of the problem: https://domysee.com/blogposts/vscode-vertical-tabs.
I'm using it and it has been quiet good until now.

Unfortunately, @tpougy, I can't seem to force both sidebars to one side (left):

I can't seem to force both sidebars to one side

Yeah that's why I'm not using this workaround

The most convenient location of tabs, for me

It would be nice to have both views, an explorer and a tab list editor in the same area, on right side. This way, main view with opened editor would not jump left and right when closing and opening explorer (CMD + SHIFT + B)

@frontendbro, @huyz, and @dvakatsiienko, https://github.com/microsoft/vscode/issues/183084#issue-1718677970

Commenting to keep this alive.

Commenting to keep this alive.

Wow im still receiving email about this.
It hasnt been implemented yet! ahahha

My comment seems to be hidden in the mass again, but it's really not that hard to change a couple settings yourself and get 90% of the way there, so reposting it again here.
After reading through this thread I've applied the following settings to my VSCode to achieve the result I was looking for which is basically vertical tabs (but slightly better because the extra functions in the Open Editors pane is pretty nice).
{
    "workbench.sideBar.location": "left",
    "explorer.openEditors.visible": 40,
    "explorer.openEditors.sortOrder": "alphabetical",
    "workbench.editor.showTabs": false
}

I then moved my Open Editors pane into the Side Panel on the right and I have the following result:

It's a hack at most, and does not replace the tabs. Everyone knows these workarounds. They don't cut it.On 2023-09-01, at 20:17, Luke Towers @.***> wrote:
My comment seems to be hidden in the mass again, but it's really not that hard to change a couple settings yourself and get 90% of the way there, so reposting it again here.
After reading through this thread I've applied the following settings to my VSCode to achieve the result I was looking for which is basically vertical tabs (but slightly better because the extra functions in the Open Editors pane is pretty nice).
{
"workbench.sideBar.location": "left",
"explorer.openEditors.visible": 40,
"explorer.openEditors.sortOrder": "alphabetical",
"workbench.editor.showTabs": false
}
I then moved my Open Editors pane into the Side Panel on the right and I have the following result:
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@LukeTowers Are there key bindings to cycle previous/next editor like with tabs? Also if you remove the sort order option does it retain the manual order?

Never tried, so I'm not sure. It works well enough for me 🤷 I jump between so many files all the time that I don't care to spend any time manually sorting them.

The best tab system is whats supported in VS 2022.
Where it separates open tabs by what library they are from.
This allows for a ton of tabs to be open without confusion for more complex working situations.
Very useful for Unity3D when lots of open scripts is common.

My comment seems to be hidden in the mass again, but it's really not that hard to change a couple settings yourself and get 90% of the way there, so reposting it again here.
After reading through this thread I've applied the following settings to my VSCode to achieve the result I was looking for which is basically vertical tabs (but slightly better because the extra functions in the Open Editors pane is pretty nice).
{
    "workbench.sideBar.location": "left",
    "explorer.openEditors.visible": 40,
    "explorer.openEditors.sortOrder": "alphabetical",
    "workbench.editor.showTabs": false
}

I then moved my Open Editors pane into the Side Panel on the right and I have the following result:

Maybe I missed something, but for me to get this to work I had to

Change the .vscode/settings.json
Select View > Appearance > Secondary Side Bar
Use the Command Pallette (Ctrl + Shift + P) to "Focus on Open Editors View" to get the view to appear in the Primary Side bar
Drag that view into the Secondary Side Bar.

I do hope this is enough to stop me from going slowly crazy over never being able to find my tabs...

Maybe I missed something, but for me to get this to work I had to

Change the .vscode/settings.json
Select View > Appearance > Secondary Side Bar
Use the Command Pallette (Ctrl + Shift + P) to "Focus on Open Editors View" to get the view to appear in the Primary Side bar
Drag that view into the Secondary Side Bar.

I do hope this is enough to stop me from going slowly crazy over never being able to find my tabs...

still not on-par with jetbrains.

what if I want all sidebars to be on the left? that doesn't work.
if I have multiple files with the same name open, I need to widen the open editors bar by quite a bit to see which file is which.
and they just do not feel right.

Sorry to bump this, but we really need this feature

Sorry to bump this, but we really need this feature

Sorry to bump this, but we really need this feature

FYI you can get this by using the "Open Editors" view on the right. However top tabs still show up but at least it works.
However is not nearly as nice as VS 2022 version which organizes by .csproj

that is not vertical tabs. That shows ALL groups, and i dont want to see the others groups tabs.
One group i use it for my backend info, another for my frontend, another for my admin panel.
i switch fast with CMD + # number, and i would like to have the tabs of that group vertically instead of horizontal

Sorry to bump this, but we really need this feature

👋 Hi @alanxp would you be willing to sponsor a VS Code extension that gives you the functionality you are looking for (as grouping by C# projects as @zezba9000 showed in VS 2022)?
We can attempt to build a small VS Code extension that helps with this, as surely many other users can also benefit from this.
Cc:	 @msuthar09 if interested in contributing

hi all!

to those who use the Move "Open Editors" view as a tab onto secondary sidebar, ...
you may find this issue useful: "Support loading/storing view layout/locations in settings.json"
https://github.com/microsoft/vscode/issues/198611
as it would allow even this workaround to be toolable and easily shareable :-)
upvote that issue if you too want to be able to share this "hack" for the meantime with your peers or project wide setting configurations 😃

/cc @santiagopuentep @pilattebe @LukeTowers @RokeJulianLockhart @dvakatsiienko @KeithWM
citations

... improving panels to to be able to place them on a new column (for example a column with all the panels and one with the Opened Editors panel) or to the other side of the screen (to have some to the right and some to the left) I think could be a great way to solve vertical tabs + adding new possibilities for the other panels too.
- @ santiagopuentep at https://github.com/microsoft/vscode/issues/108264#issuecomment-715451624

Open Editors can now be pinned on the side since 1.64 (January 2022).
- @ pilattebe at https://github.com/microsoft/vscode/issues/108264#issuecomment-1030635615

... moved my Open Editors pane into the Side Panel on the right
- @ LukeTowers https://github.com/microsoft/vscode/issues/108264#issuecomment-1068283208
https://github.com/microsoft/vscode/issues/108264#issuecomment-1703083501

![Screenshots]
- @ RokeJulianLockhart at https://github.com/microsoft/vscode/issues/108264#issuecomment-1553223336
- @ dvakatsiienko at https://github.com/microsoft/vscode/issues/108264#issuecomment-1554184304

... Drag that view into the Secondary Side Bar.
- @ KeithWM https://github.com/microsoft/vscode/issues/108264#issuecomment-1807225419

Thanks your idea, Drag "open editors" to side bar could resolve this issue

hi all!

to those who use the Move "Open Editors" view as a tab onto secondary sidebar, ...
you may find this issue useful: "Support loading/storing view layout/locations in settings.json"
Support loading/storing view layout/locations in settings.json #198611

it would allow even this workaround to be toolable and easily shareable :-)
upvote that issue if you too want to be able to share this "hack" meanwhile in a copy-pasteable form with your peers or project wide configurations 😃
for those who want this "open editors" tab to be isolated, but are disappointed by primary/secondary bars at different side: that issue can help you too: upvote and comment about being able to assign shortcut to custom tabs.
/cc @santiagopuentep @pilattebe @LukeTowers @RokeJulianLockhart @dvakatsiienko @KeithWM
citations

Bumping the feature request once again.

Is it possible to configure the vertical height of the Open Editor tabs? They are too small for me...
Judging by this issue from 2.5 years ago, there isn't...

https://github.com/microsoft/vscode/issues/108264#issuecomment-1948001439

@JodokF, that's irrelevant to this issue.

One of the biggest problems with vscode in general is its not really an IDE at an intrinsic way. It feeds into these kinds of issues when you think about it.
By this I mean lang plugins can't feed it what files are part of a solution / workspace. They can't extend a common create new project splash window, file menu etc. Everything now has to be some new lang specific view hack, the folder scanning is annoying, confusing and o did I say annoying. End up making it so you need to reinvent work for no reason (like DevKit). This text editor toy that pretends to be an IDE feels like a JS/TS dev failed to understand how actual powerful "real" langs just break down here.
I've really tried to like vscode but I just can't be productive in it. Its a huge regression from MonoDev, Rider and VS. Its only value is it runs on ARM64 Linux at this point for me. But the endless config json hell just keeps pushing me away. I shouldn't need to have to remember these json file nightmares just to create a test project and have debugging working.
Point is its so fundamentally flawed as an IDE at its core all langs outside JS/TS will end up having issues trying to do anything serious. Really wish there was a Avalonia IDE at this point. Something just as portable but designed like normal IDEs are. Something akin to a modern portable MonoDev IDE like we had what in 2003? Its kinda sad tbh.

 It also has no UI for lang specific settings in the way someone might want and the endless fragmentation in the launch.json or in .vscode folder in general is something I should never have to touch in an IDE (like .vs, .idea, folders etc). As these are environment IDE config files that shouldn't be pushed to Git yet they are so verbose you might want to. I'd honestly just support Rider IDE at this point. MS discissions around IDEs seems to be driven my TS/JS devs who forgot what an actual lang needs in this space. Thats my feeling at least.
Its really sad to. I can go back to old Ubuntu versions and install MonoDevelop which was a fully featured C# IDE + many other langs done correctly (C/C++ is way easier to get working in MonoDev). MS basically bought competition then shut it down. I've followed this for so long I've heard all the excuses.
At the end of the day if you want to get work done outside Windows, use Rider. MS is really just doing IP damage at this point IMO when it comes to IDEs.

PRs welcomed

No, This is what the official should implement !

@625781186

No, This is what the official should implement !

How much did you pay for the customer support you're demanding? You should either contribute money or code.

@625781186

No, This is what the official should implement !

How much did you pay for the customer support you're demanding? You should either contribute money or code.

I choose not to use vscode .

The Explorer side Panel has an Open Editors section which is basically vertical tabs.

* Change the .vscode/settings.json
* Select View > Appearance > Secondary Side Bar
* Use the Command Pallette (Ctrl + Shift + P) to "Focus on Open Editors View" to get the view to appear in the Primary Side bar
* Drag that view into the Secondary Side Bar.

Thanks. This gave me the closest vscode experience to what I want. I also agree that this feature should be implemented. My whole team uses vscode, so I use it out of convenience and team-continuity. This aesthetic feature would make navigating open files much easier.

Yes please to vertical tabs!

We need it, when opened very many tabs, left side tabs position is comfortable!

4 years open, and no progress...

4 years open, and no progress...

And they wont do it..
They think that they already added vertical tabs since they have like recent tabs on vertical, but they dont understand that if we make a group of tabs in another window within the same proyect, we wont have the vertical tabs that window.
Thats the problem, that they dont really understand the need of vertical tabs.
I hope they do, it would be an awesome feature and a must have

This feature is a critical accessibility concern for me. I have a severe neuromuscular disorder (SMA) and all I can use is a mouse. Using the mouse is quite strenuous so I try to rely on key bindings on my on-screen keyboard where I can to avoid having to move the mouse a lot. With many horizontal tabs I have no choice but to cycle through them sequentially to target the one I want, having to maintain a mental model of a long list. Here's an example (turn sound on):
https://github.com/user-attachments/assets/26b3286a-1d2d-4472-a586-e542e669833a
With vertical tabs there is much less of a cognitive burden because one is able to see the most proximate 30-40 tabs rather than only ~10 or less. Additionally, I can not only cycle through them more efficiently but I can target them more easily with voice commands to move the mouse to specific areas on the screen or even use AI that is able to see what I see.
The proposed workaround to use the Open Editors view in lieu of tabs is insufficient for the following reasons:

Visually they are not tabs but rather a simple list of files plus a very small icon, this causes eyestrain just as much as having to quickly cycle through dozens of tabs sequentially (luckily I don't have epilepsy)
Files with the same base name don't expand to include more of the path so there are duplicate entries without context until you go to it
The list of files is global rather than per editor as one would expect to reduce clutter and have logical groupings
The default location is underneath the file explorer which means it competes for visual space with the contents of the directory/repository
In order to get more visual space you have to enable the secondary side bar and drag the editors over there (remember moving around the screen is difficult let alone clicking while doing so)
If you do utilize the secondary side bar there is no way to move that between the file explorer and the editors so you have to look at the directory structure on one side and "tabs" on the other

I wanted to update this thread regarding vertical tabs implementation. After discussing this feature with the Theia IDE community (https://github.com/eclipse-theia/theia/discussions/13974), I've submitted a formal feature request in their repository: https://github.com/eclipse-theia/theia/issues/13979
Given Theia's high level of API compatibility with VS Code, I'm seriously considering switching to Theia if they implement vertical tabs. I believe many developers here might feel the same way.
If you're as eager for vertical tabs as I am, I encourage you to show your support by upvoting the Theia issue. A strong show of interest could accelerate the feature's development and potentially influence other IDEs (including VS Code) to reconsider its implementation.
This could be a significant step forward for those of us who've been advocating for vertical tabs. Let's show there's real demand for this feature across the developer community.
Thank you for your continued interest and support on this issue!

how about this feature?
is it implemented in the latest vscode?
:)
I have been waiting for this feature for around 2 years: Move editor tab of vscode to left side

After doing a bit of research I finally have found what I think is the best approach.
This extensión allows you to group tabs vertically and the do not display with the "annoying" long path on the right side of the filename.
https://marketplace.visualstudio.com/items?itemName=jiapeiyao.tab-group

Groups can be named and sorted.
Additionally tabs can be hidden or just show the one you're working on (VSCode appearance options can do it).

@call0fcode Turn tabs to a copy of Explorer with a lot of manual work? Thanks, no.

@call0fcode

After doing a bit of research I finally have found what I think is the best approach.

thanks for sharing it. Looks pretty nice for me. Especially when placed in the secondary sidebar apart form Primary one with the project folders explorer. The only thing I am missing now - is the possibility to let the Primary and Secondary sidebars sit on the same side of the vscode. Like this
┌──────────────────────────────────────┐
│ Title + Breadcrumbs                  │
├──────────┬────────┬──────────────────┤
│ Explorer |  Tab   │   Editor space   │
│          │ Groups │                  │
│          │        │                  │
│          │        │                  │
│          │        │                  │
│          │        │                  │
└──────────┴────────┴──────────────────┘

Doesn't seem to be a complex task to implement for monaco editor. Unfortunately it could not be fixed by user styles, since the sidebars and editor space are resizable and its' widths are calculated based on user input.

VS Code already has vertical tabs in the sidebar by default. Maybe you disabled them by accident.
Come to think of it, the horizontal tab bar is redundant. I just went ahead and disabled it.
Yes, you can't see them when you search, do source control, install extensions, etc., but do you really need to see both of those at once?

Another extension which adds vertical tabs is Better Open Editors. I tend to keep it docked to the right side of my workspace and keep the standard explorer on the left side. Works pretty well, but still not as nice a Visual Studio 2022's vertical tabs.
Here is a picture of my setup:

Also add the ability to place the tabs at the bottom - I use vscode in full screen on a mac and all day long I'm fighting with the top menu that keep showing up every time I move the mouse to the upper side of the screen to change the tabs. The menu is hiding the tabs and so the result is that a lot of times when I want to change a tab the very action of moving the mouse to that tab is hiding it (with the menu)... Can't be that I'm the only one who's facing that issue daily.
If I could move the tabs to the bottom of the editor area I won't have the menu bar hiding the tabs (but it needs to be above the status bar, not all the way at the bottom of the window since then if it will be at the very end of the screen it will collide with the mac dock that shows up in full screen and then the problem is the same).
I would've open a new request but I saw that there was already a request for that (65193) which was marked as a duplicate of this request.


Interactive r fix 134

Resolves issue with interactivity issues in R while debugging, caused by NA returned by getopt::get_Rscript_filename() function when run interactively.
Develop merged in develop (last commit ce57fc9), no issues, includes develop-refactoring changes so should merge in ok.
Ran:

regression test: all passed;
unit test: all passed;
coverage test: all passed and at 69% cover.

Vignette runs fine, all outputs normal, timings:
real	2m4.584s
user	2m43.653s
sys	0m4.082s
:exclamation: Not yet run on full-size dataset, will run this 24th Feb to confirm no issues on real data.

@flic thanks :-)


In cli  vm creation storage account error

It will work by adding "--use-unmanaged-disk" and "--admin-username"


svgRenderType change creates new outputScale field

When the svgRenderType pulldown is used, a new outputScale field is being added to the interface panel http://www.giphy.com/gifs/7JaHZgW32gFeWMAOFx

ru roh! Thanks for filing this issue - and for the gif explanation. We'll get cracking on a fix and ping you when it's up!

Fixed in https://github.com/Anemy/svgurt/pull/21 Thanks again for taking the time to report this issue! :D