#26

@NothingIsLost : CodeMirror Options shows a block reference on a line by itself as an indented block with a border around it. So, visually it stands out from the host text. If I understand @TfTHacker’s proposal it is to make a block reference integrated into the host text so it does not stand out (like a sore thumb, for me), albeit with a discrete marker to indicate it is a transclusion.

BTW, I do appreciate CodeMirror Options and use it. I am transitioning over to Live Preview, so hopefully CMO will be amended.

#27

Klaas, I appreciate you trying to help but I’m aware of the use case and how the plugin works.

d3BiZODx7C

I’m not suggesting anyone use CodeMirror Options as a solution to this FR, merely suggesting an option for conditional handling of inline block refs based on their location on the line.

I plan on adopting whatever Obsidian ends up going with so that people who can’t migrate off of CM5 still have a Live Preview option that matches as closely as possible with the CM6 version.

3 Likes
#29

Dropping a block embed into a > quote doesn’t work for me for two reasons:

  1. It’s a kludge
 Why should users have to put a block inside a blockquote to indicate it’s a block? The present arrangement is far more intuitive.

  2. What happens if the user wants to include an inline embed inside a blockquote? How would you tell the two apart?

It’s possible the programmers might be able to detect when an embed is the only thing on a line and wrap a <div class=“block-embed”> (for example) around it, but there are other complications. e.g. What if the user writes the following?

![[Embedded note]] ^reference

I still think having a different leading symbol to indicate an inline embed is the simplest answer—but, personally, I don’t have any problem with the current arrangement.

1 Like
#30

I also support this FR, we may even be able to differentiate block and span style embeds using the ! / @ syntax as proposed here.

Ideally, preferred symbols would even be customisable.

#31

Please no changing embed syntax. Handle as @NothingIsLost suggested: be aware of inline and own line and use span or div accordingly. I don’t want to have to remember @ embeds and ! embeds etc. If this is adopted it should be backwards compatible with all my lovely own-line embeds. I don’t really use inline embeds ever, so wouldn’t benefit from this change, but would be annoyed if my existing embeds broke.

7 Likes
#32

I would rather see it as a (shorthand) addition rather than a replacement as well.

#33

+1 I also support this proposal. I use custom CSS to get this effect, but it would be wonderful to have it working across themes.

#35

A common use case for me is to connect quotes from literature notes to a text that I am writing, such as this:

Screen Shot 2021-11-17 at 12.44.20 pm
Screen Shot 2021-11-17 at 12.44.20 pm1926×196 39.4 KB

The CSS snippet I have makes this look great and fluid, and I can still go back to the original note to check on the context of the quote. Without the kind of inline embeds @TfTHacker proposes, it looks like this:

Screen Shot 2021-11-17 at 12.44.42 pm
Screen Shot 2021-11-17 at 12.44.42 pm1926×450 45.6 KB

It makes it very unpleasant to read (let alone export). Even if it was a block quote I would much prefer a minimal version.

I think inline embeds would just add functionality, rather than take away anything from existing usage, and consistency across themes and modes (without having to rely on css snippets) would be great!

5 Likes
#36

Plus one - this would be a game changer for using obsidian for grant writing, since a lot of verbiage is repeated in several places in the proposal.

I wasn’t aware in-line embedding is available in other PKMs - this is the type of differentiator that would make me consider changing platforms.

1 Like
#37

@Kabo : with what CSS code do you you achieve inline embeds? I only the “out-of-line” ones because I don’t how to achieve inline. Of course, I could wait till TfTHackers plug-in is there.

#38

it’s the snippet from @smurfman111 ( I just changed the colour
)

#39

@Kabo thanks, I missed it when I read his comment.

1 Like
#40

No worries! :blush:

#41

+1 for this idea

#42

9 posts were merged into an existing topic: More concise (inline) block reference syntax

#49

Love this. Please realize it.

1 Like
#50

Many a times, while writing in Obsidian, I have felt a need to reference a particular block of words in that line. Having this feature would indeed be devine.

However, “how would this addition play with other things ?” I wonder . And, there is still the fact of block referencing not being a standard feature across PKM mediums. Roam and Obisidan handle block referencing in separate ways. Keeping this in mind, I try to avoid using block referencing as sparsely as possible. Avoid it altogether, if I can.

#51

YES!!.. I do references on bullets all the time and it looks crappy.

1 Like
#52

+1 for this. I don’t use block references much due to the rendering but I would love to use them with the inline rendering proposed above.

2 Likes
#53

@allan:
@smurfman111 's code works like a dream.