Internal Link Shortcuts

Contribuir Funcionalidade
1

Today I was looking for a way to link to a post in the same topic.

The :link: icon, when clicked, shows post #4, so I tried: using #4 and post#4, only to get frustrated, but discovering that the # character pops up categories to link (which I read about extensively since, in meta.)

Now, I find this quite inconsistent, and would like to propose ways to consistently address internal links that matches the actual URL format, or already used patterns…

Generic Patterns

Using colon as a prefix or separator would be nice, but it already autocompletes to emoticons and that could become messy. But consider: :4, :10:4, and 3:10:4 (with optional colon prefix) to link to post number 4 in the current topic, post number 4 in topic 10, and post number 4 in topic 10 of category 3.

Using / instead might work, but then it should match the URL, e.g., /c/3, /t/10, and /t/10/4.

The “quote reply” to a post uses keyword colon number, e.g., post:4 or topic:123. This can be very useful is there’s a way to show these IDs with every post (e.g., with an element title or tooltip).

In general though, #post_4 would use the actual anchor in the HTML. #4 would be great too, but it conflicts with the (current) category shortcut (BTW, what happens when you have a category name matching a tag name?)

Both solutions though are problematic for i10n since they impose English words.

The shortcut to a post in the current topic should make category and topic implicit.

Since topic IDs are global, .. can be useful, as in .[optional topic ID].[post number], e.g.:

  • ..4 to link to post #4 in current topic
  • .10.4 to link to post #4 in topic 10
1 curtida
2

Use the URL to the post. You can also edit the URL to make it refer to a specific post number in the topic as needed.

1 curtida
3

But that requires using the mouse instead of the keyboard, doesn’t it?

1 curtida
4

You can use j and k to navigate through the posts and the URL changes accordingly, so you can ^L^C to copy the URL of the current post.

Except it’s off by one:

https://meta.discourse.org/t/url-off-by-one-when-moving-through-posts-with-keyboard/50925

4 curtidas
7

Existe alguma maneira de usar URLs relativas, por exemplo, /t/50904 em vez de https://meta.discourse.org/t/50904?

teste apenas colando a URL completa: Internal Link Shortcuts - #4 by pfaffman

(só tentando entender o conceito de usar a URL completa para referenciar um link no mesmo servidor, o que parece arriscar a obsolescência do protocolo ou do nome de host… no meu caso, tenho uma instância do Discourse http: atrás do firewall que ainda não migrámos para TLS, então, se tivermos vários links internos http:, teremos links quebrados quando as URLs mudarem para https:?)

8

HTML padrĂŁo deve funcionar

<a href="/t/internal-link-shortcuts/50904/6">Link</a> deve se tornar Link.

Markdown também deve funcionar com

[Link](/t/internal-link-shortcuts/50904/6) se torna Link

4 curtidas
9

A menos que você ache que todos os usuários, toda vez, vão reescrever suas URLs agora sem nenhum benefício imediato, você precisará fazer um mapeamento ao mudar os protocolos de qualquer forma. Claro, você pode estar disposto a fazer isso ao compor URLs, mas a maioria das pessoas não fará. Não é grande coisa fazer um mapeamento de http://seudominio/ para https://seudominio.

É o tipo de coisa que nós, da área de computação, nos preocupamos e que realmente não faz diferença. É realmente, realmente difícil, mas você deve deixar isso para lá. :wink:

2 curtidas
10

tentando… com /t/50904/6

link para o post 6

yay! obrigado

4 curtidas
Post Collections, Topic-to-Topic Navigation Buttons, Menus, Anchor Links, and Topic TOC