-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening files In same tab, new tab, or new window: A flexible & consistent UI proposal #1000
Comments
That would be great. Is there any way to open a file in a new tab in an existing window now? Every time I try, it will also open in a new window, not a new tab, no matter what I do. The only way to use multiple tabs in Typora at this moment seems to be when creating new files? I hope I'm wrong. |
I've found one method solution so far: Window->Merge all windows. Not ideal, because you may not want to merge all windows (that is not minimized), but at least there is a way. |
@gandalfsaxe, if you're talking about macOS, it sounds like you want to turn on the “Prefer tabs when opening documents” option in sysprefs. With this on (set to Always), existing files open in new tabs for me in Typora. |
Ah yes that's nice. Still doesn't negate the need for manual control in Typora (I like @vassudanagunta 's proposal), but I do prefer tabs most of the time, and while there seems to be no way to combining window, you can always pull out a tab to it's own window. |
please make open files in current window on simple click.... |
@EvgenyVetrov I believe my design above satisfies your desires. Yes? |
@abnerlee I edited the proposal to make it easier to understand, and I added some more info. Where do you stand on it? It is one of the most upvoted Issues :) |
@vassudanagunta again, thanks for your proposal. Currently, or in near feature, I would prefer provide the option I think navigate (#1154) would be needed if we want to support open in same tab. |
just vscode but without the preview, turns out I don't need rendering, let alone wysiwyg, syntax coloring is enough xd |
I switched from typora to VSCode+Dendron and it has changed a lot in the way I take notes. Also cross linking via [[para]] and refactorable hierarchies have been a blessing. I still use typora sometimes as a secondary editor for long form content but that is 2% of the times I use it for markdown now. I should also add that dendron in it's current state is more suited for developers and may feel overwhelming or confusing if you do not use IDEs or advanced text editors. |
Open links in same window is the most useful and obvious feature that Typora does not have. Sorry, but this is an APP that I use everyday and love. It's just dumb, stubborn and stupid that this simple feature is not available. Yes and I have purchased it. |
I just wanted to comment on MarkText. I think it's an awesome initiative but it's not at the level of Typora in various ways yet. The Markdown it produces is much messier (many empty lines in output). The editor also often scrolls unpredictably which makes it rather frustrating to use. However, it does offer tabs and is a very nice program that I think has the most potential for the future. The devs made some major improvements in the most recent release and seem to be very receptive to feedback. So I have no doubt that in time, it will be on par with Typora in all the ways that it is weaker. Personally, I think Typora is awesome with the main omission being tabs or simply the ability to open documents easily within the current window. I personally don't care as much about tabs, but having a new window popup when you search for a document is a bit of a dealbreaker (for me). One of the areas that Typora also suffers is the English translation. The grammar in the application is not quite right for those of us who are native English speakers. MarkText seems to be much better in that regard IMHO. |
Would just like to bump up this issue, as it looks like a lot of people really want this feature to happen and I am one of them. |
Hi, i'm like use to typora, but i don't konw why this is miss. So, please, because no other method can compare with the built-in function. |
No one NEEDS tabs! Use text mode and edit your markdown with vim! |
Sorry, last time I wrote my beauty blog in vim ended I could not quit so reinstalled OS on my Mac in service center. |
@blurayne please don't spam Typora users with your personal opinion here. It's both silly and obnoxious. If you want to convert people, write a blog post, or tweet your one liner if you can't be bothered to write more. |
The silly thing is that I paid for that thing and there seems IS NO Linux support and users are treated like garbage. The WYSIWYM editor is the best among the Markdown editors I tested. But unfortunately there only seems to be some Mac/Windows maintenance and features people demand are not really discussed since the devs are very close minded. You can have a strong opinions - sure - that is what makes Typora to what it is. Simply but also very strong and well thought. But please don't just use pseudo-arguments and just close tickets. GitHub issues is a place for OpenSource. If you want dictatorship please open your own bug tracker! Take as example a tab: sure you can use your windows manager for tiling or tab switch but the real issue ist a) you can open the same file over and over again b) you may end up with a long list of windows that are better suited in a window with tabs. So, your argument NOT to implement this feature is... ?! |
You had a free trial period to figure this out, and even 30 days to get a refund. While I don't agree with all of @abnerlee's decisions he doesn't act as you say. You just happen to not like his decisions.
Exactly. Why do you think there aren't more competitors or better? Yet you whine and act entitled to have even more for $15 even though nothing was promised other than the product as it stood when you bought it and you had plenty of time to evaluate it before paying.
This is not a subscription model. Why does anybody get to demand anything more than what they got? Jeezus, the entitlement of people these days. If @abnerlee fails to meet peoples expectations for $15, he will go out of business. If better products come out for $15 or even $30 he will also likely go out of business. But where are they?
No, it's just that you don't like them. As I said, I don't agree with many of @abnerlee's decisions, but I don't act entitled and unappreciative as you do.
I'd rather he close tickets that he doesn't intend to address rather than keeping them open and implying that he will address them. If he is making bad decision after bad decision, then everybody would jump ship for another solution. There's MarkText, for example. Why don't you switch to that? It's open source, and you can fork and implement all these things you think are easy to decide and implement. I'd like to see how you do. Oh wait. You've contributed zilch to the community in the past year (and despite all the fluff in your bio). From the looks of it you've never contributed anything anyone has found useful. Ever. Oh sorry. I forgot about the great wisdom that you so freely and kindly gift to people.
That's long been NOT true. Open source is just given a free ride. And a quick glance at the (logged out) home page and pricing plans confirms not only this, but that free rides are also given to non-open source.
I have no clue what you're saying here, but I'm done. I don't have time to school you. Typora does support tabs. My proposal above is about UX. It's a nice-to-have, and I think it would make Typora more elegant and easy to use. That's it. Bye! [Note to self: Why do I waste my time on people with attitudes like this?] |
Voting for this feature - this is basically the only thing that feels lacking in any way for me with how I use Typora. |
Forget - its dead. |
The simple solution—at least, which works just fine for me—is:
NOTE: Quit Typora before running the above command in a terminal. New "open docs as tabs behaviour" will take effect when Typora is next launched. You can change |
There are a lot of comments on this issue, but I think the current status is that there is still no way to make it use tabs at all if you're using it with Windows? And there isn't any recommended alternative WYSIWYG MD editor? Edit: I ended up switching to https://obsidian.md/. It does quite a bit more than just editing MD files, but it ended up being a good solution for me. And it uses tabs (except it doesn't open new files in a new tab by default, but at least it offers tabs). |
Agree - no way to use this on Windows. Try Joplin. |
I tried Joplin, but it isn't designed to edit your own MD files, it stores your notes in its own data vault (you can export the notes, but I wanted something that can edit MD files in a folder as they are). |
Now that I see the state of abandonment in these issues, I regret that I bought Typora today in 2024. |
@cvzakharchenko , I too wish for some Typora improvements (most notably folding code blocks), but I still think that at $15 for a lifetime license, Typora brings amazing value to my workflow (and I've tried a lot of apps). |
Thanks for an interesting write-up! I agree, that $15 for a lifetime is a steal. And despite so many other options, nothing is really perfect. But I still wish linking would work better in Typora.
|
I was also looking for the ability to open multiple documents in one Typora application window using tabs (in Windows 11). The workaround I've found that allows tabs while using Typora is a utility called 'Groupy' (from Stardock). It's unfortunately not free but it does have a 30-day trial which I'm using in the meantime..... Still hoping for Typora to support this natively though ;-) |
This feature would enhance usability, as Typora currently opens each file in a separate window when multiple files are viewed, leading to a cluttered workspace that requires significant effort to manage effectively. Therefore, I would also like to request the addition of a single-window mode option in Windows 11 that would allow users to open multiple Markdown files within the same Typora window, either as tabs or by replacing the current document. |
A tab system is really something we are all waiting to see. As a user and as a UX designer testing it out, Typora is an amazing, comfortable and accessible tool and offer a large choice of preference. But despite all that , without possibility to open multiple file in the same windows, even MS Notepad is currently more productive. looking forward to see new versions implementing it |
@Asta007 Typora already does support tabs, at least in macOS. You have to create a new blank tab, and then manually look for the link target. It makes Typora a poor choice for editing a set of interlinked documents. |
In Linux, everytime opening a file, it will create a new window. That is too slow. Please provide a way to open a file (using |
There are three ways files can be opened:
Everyone prefers a different thing. The way to satisfy everyone is to let them configure default behavior, and to give them a an easy way to override the default by holding down a meta key.
(This proposal is intended to apply to all platforms, but the specifics below are given only for macOS.)
File menu: customizable
New
andOpen
behaviorSafari has an "Open Pages in Tabs Instead of Windows" setting. I propose Typora have a similar setting that governs
File:New
andFile:Open
menu commands:"Open files in
same tab
|new tab
|new window
" (dropdown selection)Regardless of this setting, users can at any time get any of the other behaviors by holding down a meta-key while clicking on the menu command (see below).1
Sidebar navigation
The sidebar is perceived as a navigation bar. People expect navigation to take place in the same view port, i.e. in the same tab. In almost all apps, including web browsers, nav bar clicks by default open items in the current tab.
Meta keys can be used to get different behavior (see below). This is how most other apps work.
Markdown link navigation
Since the main task in an editor is editing, clicks on Markdown links should support editing them, either by showing the underlying link markup and placing the cursor, or as described in #1313.
But users will also want to navigate the links, to preview how, for example, their website will work. Again, the same meta keys can be used to get the desired nav behavior.
Meta-key Overrides
The same meta key combinations should govern all of the above cases, to override the default behavior in the same way.
Consistency avoids user confusion, and facilitates muscle memory.
⌘
⌘⇧
⌘⌥
(no meta key)
File:New
keyboard shortcutFile:Open
keyboard shortcutFile:New
orFile:Open
menu item(⌘K to edit URL)
Footnotes
It would be nice to be consistent with Safari, the app where most people on macOS develop their muscle memory for tab-oriented keyboard shortcuts. Safari has a nice feature: The "Open Pages in Tabs Instead of Windows" also governs the the meta key mappings, such that the selected default behavior gets the easier ⌘-click and the other behavior gets the ⌘⌥-click. Typora could do that too. Essentially when a user chooses a different default, we swap the columns in the above table. ↩
The text was updated successfully, but these errors were encountered: