> > yes, except elisp variables are *not* case sensitive.
>
> You mean... they *are* case-sensitive, right?
indeed! .
> Mh.. if fu-bar and FU-BAR are two different variables, I guess we
> should rename one of name anyway. Hence my initial proposal :)
i agree -- having two variable names that
Greg Minshall writes:
>> IMHO this rather call for making C-h v (and C-h f) case-non-sensitive.
>
> yes, except elisp variables are *not* case sensitive.
You mean... they *are* case-sensitive, right?
> so, if fu-bar and FOO-BAR are different variables, would C-h v put
> up (some sort of) a dial
hi, Bastien,
> IMHO this rather call for making C-h v (and C-h f) case-non-sensitive.
yes, except elisp variables are *not* case sensitive. so, if fu-bar and
FOO-BAR are different variables, would C-h v put up (some sort of) a
dialog to choose between them? it would be slightly messy.
cheers,
I will.
- Carsten
On 26 apr. 2013, at 12:27, Suvayu Ali wrote:
> Hi Carsten,
>
> On Fri, Apr 26, 2013 at 12:11:46PM +0200, Carsten Dominik wrote:
>>
>> On 26 apr. 2013, at 11:59, Suvayu Ali wrote:
>>
>>> I did a query-replace-regexp: @var{\([^}]+\)} -> @code{\1}. Hopefully I
>>> skipped th
Hi Carsten,
On Fri, Apr 26, 2013 at 12:11:46PM +0200, Carsten Dominik wrote:
>
> On 26 apr. 2013, at 11:59, Suvayu Ali wrote:
>
> > I did a query-replace-regexp: @var{\([^}]+\)} -> @code{\1}. Hopefully I
> > skipped the right ones; patch is attached.
>
> Do you have write access? If so, plea
On 26 apr. 2013, at 11:59, Suvayu Ali wrote:
> Hi Bastien and Carsten,
>
> On Fri, Apr 26, 2013 at 11:27:04AM +0200, Bastien wrote:
>> Carsten Dominik writes:
>>
>>> Yes, I agree. Let's wait for Bastien to take a last look at this,
>>> but it should indeed be reverted.
>>
>> Oh, I wasn't aw
Carsten Dominik writes:
> Yes, I agree. Let's wait for Bastien to take a last look at this,
> but it should indeed be reverted.
Oh, I wasn't aware of this "metasyntactical" notion.
No problem for reverting this change -- please make this
in the maint branch so that users of 8.0.2 enjoy this.
Al
On 26 apr. 2013, at 10:41, Suvayu Ali wrote:
> Hi Carsten,
>
> On Fri, Apr 26, 2013 at 10:10:32AM +0200, Carsten Dominik wrote:
>>
>> I suspect that the cases you are talking about here are due
>> to incorrect use of the texinfo command @var{}. This should
>> only be used for metasyntactical
Hi Carsten,
On Fri, Apr 26, 2013 at 10:10:32AM +0200, Carsten Dominik wrote:
>
> I suspect that the cases you are talking about here are due
> to incorrect use of the texinfo command @var{}. This should
> only be used for metasyntactical variables, when they stand
> for something else in a descr
On 26 apr. 2013, at 01:48, Suvayu Ali wrote:
> On Thu, Apr 25, 2013 at 07:37:25PM -0400, Greg Minshall wrote:
>> sorry about that. i was going to ask about the variable names in the
>> current (8.x) documentation being in upper case. (then, wanted to check
>
> [...chomp...chomp...chomp...]
>
Hi Suvayu,
Suvayu Ali writes:
> I believe that would be incorrect behaviour.
> If I'm not mistaken,
> emacs-lisp variable names are case sensitive.
>
> (setq test "lower case"
> TEST "UPPER CASE")
>
> (message "%s, %s" test TEST)
Sure, variable names are case sensitive, but it
On 26 apr. 2013, at 01:48, Suvayu Ali wrote:
> On Thu, Apr 25, 2013 at 07:37:25PM -0400, Greg Minshall wrote:
>> sorry about that. i was going to ask about the variable names in the
>> current (8.x) documentation being in upper case. (then, wanted to check
>
> [...chomp...chomp...chomp...]
>
Hi Bastien,
On Fri, Apr 26, 2013 at 08:56:19AM +0200, Bastien wrote:
> Hi Greg,
>
> Greg Minshall writes:
>
> > but, it means that placing the cursor over the name and hitting C-h v
> > doesn't default to that name. (and, i've always found that a convenient
> > way to navigate.)
> >
> > so, ju
Hi Greg,
Greg Minshall writes:
> but, it means that placing the cursor over the name and hitting C-h v
> doesn't default to that name. (and, i've always found that a convenient
> way to navigate.)
>
> so, just curious is it might make sense to revert to lower case
> names.
IMHO this rather cal
On Thu, Apr 25, 2013 at 07:37:25PM -0400, Greg Minshall wrote:
> sorry about that. i was going to ask about the variable names in the
> current (8.x) documentation being in upper case. (then, wanted to check
[...chomp...chomp...chomp...]
> but, it means that placing the cursor over the name and
sorry about that. i was going to ask about the variable names in the
current (8.x) documentation being in upper case. (then, wanted to check
the mailing list, but hit the wrong key -- now i've looked, cursorily,
as i wanted to apologize quickly.)
this convention has the advantage of making clear
hi. the info pages seem to have convert
17 matches
Mail list logo
