Summary support

[GavinNovate]

I would love to see Typora support the summary feature.Just like this.

[abnerlee]

You could use

<details>
  <summary>Copyright 1999-2014.</summary>
  <p> - by Refsnes Data. All Rights Reserved.</p>
  <p>All content and graphics on <a href="https://typora.io" target="blank">this</a> web site are the property of the company Refsnes Data.</p>
</details>

instead now in Typora

[gt-sun]

能支持代码段吗？

View Code

```json { "kind" : "Policy", "apiVersion" : "v1", "predicates" : [ {"name" : "PodFitsHostPorts"}, {"name" : "PodFitsResources"}, {"name" : "NoDiskConflict"}, {"name" : "NoVolumeZoneConflict"}, {"name" : "MatchNodeSelector"}, {"name" : "HostName"} ], "priorities" : [ {"name" : "LeastRequestedPriority", "weight" : 1}, {"name" : "BalancedResourceAllocation", "weight" : 1}, {"name" : "ServiceSpreadingPriority", "weight" : 1}, {"name" : "EqualPriority", "weight" : 1} ] } ```

[Songkeys]

@abnerlee

Could we use markdown syntax inside <details> tags? If not, could this feature be supported?

[vidavidorra]

Any update on this feature?

This bit does not render in Typora (Version 0.9.9.25.3 (2897)). Note that i've added \ before the ` marks to ensure the code block continues.

## collapsible markdown?

<details>
  <summary>CLICK ME</summary>
  <p>

  #### yes, even hidden code blocks!

  \```python
  print("hello world!")
  \```

  </p>
</details>

Render in typora

On github

collapsible markdown?

CLICK ME

#### yes, even hidden code blocks! ```python print("hello world!") ```

[abnerlee]

relates #1939

[iTomxy]

I hope it can automatically create hierarchical folding points based on headings of all levels, just like the one in jupyter notebook.

[svonjoi]

collapsible images? typora does not rendering image inside details tag

[iTomxy]

Not image rendering. I mean something like the code folding in a code editor (example), but the folding points are the headings, i.e. treating the content within the scope of heading as a code block.

[svonjoi]

hehe i understood u. I just was asking by collapsible images functionallity, not about your prev comment. Sorry for not expressing myself

[Squirreljetpack]

+1 for something like >! syntax for a collapsible region (stackoverflow)

[aitimate]

You could use

<details>
  <summary>Copyright 1999-2014.</summary>
  <p> - by Refsnes Data. All Rights Reserved.</p>
  <p>All content and graphics on <a href="https://typora.io" target="blank">this</a> web site are the property of the company Refsnes Data.</p>
</details>

instead now in Typora

This is so bad for codes

[pdevito3]

+1

[Craaab]

It would be super nice to have contents between [```] collapsable. To be more specifically, make contents in the "well" collapsable.

[zhaoqingqing]

mark code fold

[tracyqwerty]

same problem.

<details>
<summary>Details</summary>
<p>
In C, a string is essentially an array of characters, but it's typically represented as a pointer to its first element -- a `char *`. So when you have a `char *` variable, it is effectively a string.

The `strcmp` function compares two strings. It expects as arguments two pointers to the beginning of each string (two `char *`). When you call `strcmp(wc1->word, wc2->word)`, you're saying "compare the string that begins at `wc1->word` with the string that begins at `wc2->word`".

If you were to dereference the pointers with `*wc1->word` and `*wc2->word`, you would be providing the `char` values (i.e., the first characters of each string) at those memory locations instead of the pointers themselves, which is not what `strcmp` expects.

In other words, `strcmp` doesn't want to know what the first characters of the strings are -- it wants to know where the strings start. By giving it `char *` arguments, you're providing it with that information.

</p>

</details>

[andrew-manger]

+1 to implement a Markdown version of collapsable content (no HTML) to allow for easy editing and preview.

[Pomax]

Counter-point: Typora claims to support GFM, and this is part of GFM, so instead of implementing a different markdown with detail syntax, maybe after almost a decade (it's been an active request since 2016) just support it. Or stop claiming to support GFM.

[MTDickens]

Why hasn't typora team fixed this after almost 6 yrs!