Re: [O] variable names in manual
Hi Greg, Greg Minshall minsh...@umich.edu 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 call for making C-h v (and C-h f) case-non-sensitive. Maybe you can fill an Emacs bug for this? M-x report-emacs-bug RET -- Bastien
Re: [O] variable names in manual
Hi Bastien, On Fri, Apr 26, 2013 at 08:56:19AM +0200, Bastien wrote: Hi Greg, Greg Minshall minsh...@umich.edu 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 call for making C-h v (and C-h f) case-non-sensitive. Maybe you can fill an Emacs bug for this? M-x report-emacs-bug RET 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) The above prints lower case, UPPER CASE. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] variable names in manual
On 26 apr. 2013, at 01:48, Suvayu Ali fatkasuvayu+li...@gmail.com 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...] 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. I wasn't aware of this change! I would agree with Greg here. Can you point me to a place in the manual where this is the case? Are you talking about the infor documentation or HTML documentation? - Carsten -- Suvayu Open source is the future. It sets us free.
Re: [O] variable names in manual
Hi Suvayu, Suvayu Ali fatkasuvayu+li...@gmail.com 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 would be a problem for C-h v and C-h f to be case-insensitive only for variable names that have the same names but different cases -- not sure it's a real problem then... -- Bastien
Re: [O] variable names in manual
On 26 apr. 2013, at 01:48, Suvayu Ali fatkasuvayu+li...@gmail.com 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...]
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.
I wasn't aware of this change! I would agree with Greg here.
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 description.
Here is an example from the current manual.
You can customize this behavior using the option
@var{org-table-use-standard-references}.} to use another, more general
representation that looks like this:
@example
@@@var{row}$@var{column}
@end example
The first use of @var is incorrect, @code should be used here. But the use in
@var{row} and @var{column} is correct.
I believe that a while ago we did use @var and @code correctly, but someone
went through and changed the @code{org-...} to @var{org-...} at some point. We
need to change this back.
- Carsten
--
Suvayu
Open source is the future. It sets us free.
Re: [O] variable names in manual
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 description.
Here is an example from the current manual.
You can customize this behavior using the option
@var{org-table-use-standard-references}.} to use another, more general
representation that looks like this:
@example
@@@var{row}$@var{column}
@end example
The first use of @var is incorrect, @code should be used here. But
the use in @var{row} and @var{column} is correct.
I believe that a while ago we did use @var and @code correctly, but
someone went through and changed the @code{org-...} to @var{org-...}
at some point. We need to change this back.
I believe reverting this commit should do it:
commit 7ed97e767dd4f4fbceac39a9758dbf594a4fd2fd
Author: Bastien Guerry b...@altern.org
Date: Mon Apr 15 00:51:20 2013 +0200
org.texi: Use @var{...} instead of @code{...} for variables
* org.texi: Use @var{...} instead of @code{...} for variables.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] variable names in manual
On 26 apr. 2013, at 10:41, Suvayu Ali fatkasuvayu+li...@gmail.com 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 variables, when they stand
for something else in a description.
Here is an example from the current manual.
You can customize this behavior using the option
@var{org-table-use-standard-references}.} to use another, more general
representation that looks like this:
@example
@@@var{row}$@var{column}
@end example
The first use of @var is incorrect, @code should be used here. But
the use in @var{row} and @var{column} is correct.
I believe that a while ago we did use @var and @code correctly, but
someone went through and changed the @code{org-...} to @var{org-...}
at some point. We need to change this back.
I believe reverting this commit should do it:
commit 7ed97e767dd4f4fbceac39a9758dbf594a4fd2fd
Author: Bastien Guerry b...@altern.org
Date: Mon Apr 15 00:51:20 2013 +0200
org.texi: Use @var{...} instead of @code{...} for variables
* org.texi: Use @var{...} instead of @code{...} for variables.
Yes, I agree. Let's wait for Bastien to take a last look at this, but it
should indeed be reverted.
- Carsten
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] variable names in manual
Carsten Dominik carsten.domi...@gmail.com 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.
Also, maybe the revert of this commit is not enough,
and we should check against remaining @var{...} to see
if they are okay.
--
Bastien
Re: [O] variable names in manual
On 26 apr. 2013, at 11:59, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
Hi Bastien and Carsten,
On Fri, Apr 26, 2013 at 11:27:04AM +0200, Bastien wrote:
Carsten Dominik carsten.domi...@gmail.com 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.
Also, maybe the revert of this commit is not enough,
and we should check against remaining @var{...} to see
if they are okay.
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, please install you patch.
- Carsten
Cheers,
--
Suvayu
Open source is the future. It sets us free.
0001-Switch-var-macros-to-code-for-lisp-variables.patch
Re: [O] variable names in manual
Hi Carsten,
On Fri, Apr 26, 2013 at 12:11:46PM +0200, Carsten Dominik wrote:
On 26 apr. 2013, at 11:59, Suvayu Ali fatkasuvayu+li...@gmail.com 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, please install you patch.
Sorry I do not have write access. Someone else will have to do it.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] variable names in manual
I will.
- Carsten
On 26 apr. 2013, at 12:27, Suvayu Ali fatkasuvayu+li...@gmail.com 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 fatkasuvayu+li...@gmail.com 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, please install you patch.
Sorry I do not have write access. Someone else will have to do it.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] variable names in manual
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, Greg
Re: [O] variable names in manual
Greg Minshall minsh...@umich.edu 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 dialog to choose between them? it would be slightly messy. Mh.. if fu-bar and FU-BAR are two different variables, I guess we should rename one of name anyway. Hence my initial proposal :) -- Bastien
Re: [O] variable names in manual
yes, except elisp variables are *not* case sensitive. You mean... they *are* case-sensitive, right? indeed! insert-sheepish-smiley. 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 differ only in case is a bad idea. but the language allows it. oh, well. cheers!
Re: [O] variable names in manual
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 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. I wasn't aware of this change! I would agree with Greg here. -- Suvayu Open source is the future. It sets us free.
