Early on ( ~88 ) someone told me { } were called buzzard wings.  Might not 
have caught on, but is a lot more fun.

On Sunday, December 6, 2020 at 12:18:17 PM UTC-5 [email protected] wrote:

> Ahh, I see.  Right, bracket is generic and if the documentation used 
> braces for parenthesis, it is incorrect.
>
> On Sun, Dec 6, 2020 at 11:49 AM A. Wik <[email protected]> wrote:
>
>> On Sun, 6 Dec 2020 at 16:29, Jesus Arocho <[email protected]> wrote:
>> >
>> > Not quite:
>> > () = parenthesis or round brackets
>> > {} = braces or curly brackets
>> > [ ] = brackets or square brackets
>> >
>>
>> Yes?  Not quite what?  What you write above just seems to illustrate
>> what I was saying.
>>
>> I meant that "brackets", not "braces", is the term to use if you wish
>> to refer to any kind of brackets.  The documentation uses the word
>> "braces" to refer specifically to parentheses ("round brackets").
>>
>> -aw
>>
>> -- 
>> -- 
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "vim_use" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vim_use/CALPW7mQCvsuu2HAhTA33r1Y53QzqFMG8uCrFmQYh69AuDqHwfg%40mail.gmail.com
>> .
>>
>

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_use/17a6769f-a4a7-401d-8aec-2962f8224bean%40googlegroups.com.

Reply via email to