# \#tags won't autocomplete at start of line

**URL:** https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578
**Category:** Feature
**Tags:** completed
**Created:** [24 juni 2018 om 06:03 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578 "2018-06-24T06:03:59Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [24 juni 2018 om 06:03 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/1 "2018-06-24T06:03:59Z")

</div>

A minor issue: autocompleting of tags won’t work when the # is the first character of a line.

---

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [24 juni 2018 om 06:30 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/2 "2018-06-24T06:30:06Z")

</div>

Not really a bug, but might be confusing if you are unfamiliar with markdown. Lines beginning with `#` means something in markdown, and it’d be weird if I saw a list of tags or categories every time I’m writing a header.

`# a header` renders to:

# a header

You can add a space before the `#` as a workaround.

---

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [24 juni 2018 om 06:32 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/3 "2018-06-24T06:32:53Z")

</div>

Well, the header requires a space between the # and the first character, a tag doesn’t. So technically there’s a difference, no?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [25 juni 2018 om 03:39 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/4 "2018-06-25T03:39:15Z")

</div>

Its a trade-off

- Be really annoying out of the box when you try to create titles

vs

- Autocomplete for tags/categories

I see a _minor_ feature request here which is fine for, when you are at the beginning of a line:

#b ◀ autocomplete appears.

So we basically wait one more char instead of totally giving up.

---

<div class="post-metadata">

### Author: ![renato](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/renato/32/383632_2.png) [@renato](https://meta.discourse.org/u/renato)
#### Post date: [9 november 2020 om 16:51 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/5 "2020-11-09T16:51:43Z")

</div>

> [@sam](#):
>
> I see a _minor_ feature request here which is fine for, when you are at the beginning of a line:
> 
> #b ◀ autocomplete appears.
> 
> So we basically wait one more char instead of totally giving up.

I understand it’s a minor feature request, but is this something that can be achieved somehow?

Tag autocompleting is a key feature in my community and users are just not linking to the tags because the autocomplete doesn’t show up in this specific scenario, and the post ends up with a bunch of **#Wrong-Tag-Name**.

Thanks.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [9 november 2020 om 21:47 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/6 "2020-11-09T21:47:32Z")

</div>

Certainly #pr-welcome for this refinement.

---

<div class="post-metadata">

### Author: ![Richie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/richie/32/115110_2.png) [@Richie](https://meta.discourse.org/u/Richie)
#### Post date: [14 april 2021 om 20:49 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/7 "2021-04-14T20:49:24Z")

</div>

Hi everyone,

#tag suggestions and #category suggestions only work mid-sentence and never at the start of a new line.

For example, here’s a mid-sentence example that works: #po

 ![image](https://global.discourse-cdn.com/meta/original/3X/5/d/5de7646e895a4470761a17d8f339a3631d1fdb4c.jpeg)

And here’s a new line / start of line that doesn’t work, zero suggestions are offered:

#po

 ![image](https://global.discourse-cdn.com/meta/original/3X/8/a/8a61414941d1ae0895d6c630be99749847e24169.jpeg)

I can’t seem to find any reference to it.

It provides a very mixed user experience.

Is this by design?

---

<div class="post-metadata">

### Author: ![osioke](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/osioke/32/238946_2.png) [@osioke](https://meta.discourse.org/u/osioke)
#### Post date: [15 april 2021 om 13:50 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/8 "2021-04-15T13:50:11Z")

</div>

Yes it is by design. As with conversations, you’d usually start with what you want to say then include a reference or link/tag some other conversation or material to it.

---

<div class="post-metadata">

### Author: ![renato](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/renato/32/383632_2.png) [@renato](https://meta.discourse.org/u/renato)
#### Post date: [15 april 2021 om 14:29 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/9 "2021-04-15T14:29:50Z")

</div>

Previously reported here:

> [@\#tags won't autocomplete at start of line](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578):
>
> A minor issue: autocompleting of tags won’t work when the # is the first character of a line.

It’s said to be a limitation caused by the heading markdown, usually when you’re starting a line with `#` that’s what you want.

However, I use tags extensively in my community and I’d like to target this eventually, users often mistype the tag they are trying to mention. @sam said it’s #pr-welcome (allowing the dropdown to appear when you type a letter after the `#`).

---

<div class="post-metadata">

### Author: ![osioke](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/osioke/32/238946_2.png) [@osioke](https://meta.discourse.org/u/osioke)
#### Post date: [15 april 2021 om 14:33 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/10 "2021-04-15T14:33:58Z")

</div>

I didn’t realise there was a topic for this already, so I merged the conversation here.

---

<div class="post-metadata">

### Author: ![renato](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/renato/32/383632_2.png) [@renato](https://meta.discourse.org/u/renato)
#### Post date: [14 december 2022 om 11:11 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/11 "2022-12-14T11:11:09Z")

</div>

It seems to be fixed with

> [@Hashtags are getting a #makeover](https://meta.discourse.org/t/hashtags-are-getting-a-makeover/248866):
>
> Discourse has supported linking to categories (#announcements) and tags (#release-notes) for a long time using hashtags (#). With the introduction of [Discourse Chat](https://meta.discourse.org/t/discourse-chat/230881) we wanted to be able to link to chat channels with hashtags, which required some overhauling of how the system works to allow for channels to be suggested with autocomplete and also to cook in posts and chat messages. We also decided to take the time to overhaul the design of the autocomplete menu and cooked hashtags. A summary of th…

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [17 december 2022 om 12:44 UTC](https://meta.discourse.org/t/tags-wont-autocomplete-at-start-of-line/90578/12 "2022-12-17T12:44:57Z")

</div>

This topic was automatically closed after 3 days. New replies are no longer allowed.
