# \#= Commenting =# very inconvenient on Spanish language keyboard

**URL:** <https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850>\
**Category:** Internals & Design\
**Created:** [December 19, 2017, 3:55pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850 "2017-12-19T15:55:31Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [December 20, 2017, 1:08pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/21 "2017-12-20T13:08:16Z")

</div>

> [@andyferris](#):
>
> Yes, #( … )# would have been better

My initial PR for this used `#{ ... }#` but it was shot down because of the danger of an inadvertent multiline comment, and the same objection would apply to `#(`. See the discussion in [WIP: implement #= ... =# multiline comments by stevengj · Pull Request #6128 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/pull/6128)

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [December 20, 2017, 1:51pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/22 "2017-12-20T13:51:52Z")

</div>

My comments was not intended to suggest that. I was merely pointing out the difficulty of making everything convenient for multiple layouts at the same time.

That said, while US and similar layouts are a reasonable baseline, people should of course feel free to use whatever they like.

---

<div class="post-metadata">

**Author:** ![Iagoba\_Apellaniz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/iagoba_apellaniz/32/34406_2.png) [@Iagoba\_Apellaniz](https://discourse.julialang.org/u/Iagoba_Apellaniz)\
**Post date:** [December 20, 2017, 2:35pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/23 "2017-12-20T14:35:25Z")

</div>

I’m comfortable with current approach since commenting should be done by the editor with some special shortcut.

Think that the language specifications must be always in balance between the user preferences and the compiler ones. That’s why, in my opinion using brackets would be difficult.

On the other hand I’m a full time user of [atom.io](http://atom.io), but I did not find a way on commenting via a shortcut on highlighted blocks. That’s why I wrote this [discuss.atom.io:50858](https://discuss.atom.io/t/toggle-comment-blockwise/50858).

---

<div class="post-metadata">

**Author:** ![TravisA9](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/travisa9/32/357_2.png) [@TravisA9](https://discourse.julialang.org/u/TravisA9)\
**Post date:** [December 20, 2017, 3:14pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/24 "2017-12-20T15:14:59Z")

</div>

To expand on what @mkborregaard seems to be implying:

> Oh God I hope “just use a US keyboard no matter where you are” never becomes the official recommendation.

Switching between two keyboards could/would be more of a burden than the alternatives. In my case, I have to write in Spanish and English all throughout the day so I have to choose between one or the other. I like the English language keyboard layout better for programming but the Spanish language keyboard has all the letters and symbols I need without me having to look up key-combinations on some table.

I suspect that whatever choice is settled upon it won’t be ideal for all but at least it’s being given due consideration.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [December 20, 2017, 4:47pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/25 "2017-12-20T16:47:53Z")

</div>

Feel free to open a feature request at [https://github.com/JunoLab/atom-julia-client](https://github.com/JunoLab/atom-julia-client), it should be pretty easy to implement this.

---

<div class="post-metadata">

**Author:** ![tamasgal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamasgal/32/27946_2.png) [@tamasgal](https://discourse.julialang.org/u/tamasgal)\
**Post date:** [December 20, 2017, 5:17pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/26 "2017-12-20T17:17:49Z")

</div>

Actually switch between three layouts all the time and in macOS you have a small flag in the menubar indicating which layout is active. For coding of course I have the US keyboard. Also the auto-correct features of macOS always match the current layout, so it fits that as well 😉  
For my workflow at least it has been perfectly fine for the last decade(s).

---

<div class="post-metadata">

**Author:** ![favba](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/favba/32/2735_2.png) [@favba](https://discourse.julialang.org/u/favba)\
**Post date:** [December 20, 2017, 5:58pm UTC](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850/27 "2017-12-20T17:58:17Z")

</div>

You can also set a keyboard shortcut to change between layouts. I use option+space to quickly switch US and US International layouts.

[Previous page](https://discourse.julialang.org/t/commenting-very-inconvenient-on-spanish-language-keyboard/7850.md?page=1)
