:diffsplit | verbose set fdm?
While replying to a post on the vim users' list, I noticed a slight problem. The diff commands set some options, but this is not reported with verbose set. For example :e foo.txt :set fdm=marker :diffsplit bar.txt :wincmd wback to foo.txt :verbose set fdm? foldmethod=diff :only :verbose set fdm? foldmethod=manual --Benji Fisher
Re: :diffsplit | verbose set fdm?
Benji Fisher wrote: While replying to a post on the vim users' list, I noticed a slight problem. The diff commands set some options, but this is not reported with verbose set. For example :e foo.txt :set fdm=marker :diffsplit bar.txt :wincmd wback to foo.txt :verbose set fdm? foldmethod=diff :only :verbose set fdm? foldmethod=manual --Benji Fisher Since you entered the built-in command which changed the 'fdm' option at the keyboard, there is no script or modeline to 'verbose'ly report. Or is the file actually not manually folded at the last step? I don't understand in what way the actual behaviour differs from the expected behaviour. Best regards, Tony.
Re: :diffsplit | verbose set fdm?
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Benji Fisher wrote: While replying to a post on the vim users' list, I noticed a slight problem. The diff commands set some options, but this is not reported with verbose set. For example :e foo.txt :set fdm=marker :diffsplit bar.txt :wincmd w back to foo.txt :verbose set fdm? foldmethod=diff :only :verbose set fdm? foldmethod=manual --Benji Fisher Since you entered the built-in command which changed the 'fdm' option at the keyboard, there is no script or modeline to 'verbose'ly report. Or is the file actually not manually folded at the last step? I don't understand in what way the actual behaviour differs from the expected behaviour. The copy of command itself could be remembered to be printed later by 'verbose set fdm?', like this: Last set from interactive, 33 commands ago ':diffsplit bar.txt' Or the first 80 chars of the command, in case it was too long (single vim command half million characters long was discussed recently on the list ... although it was not typed interactively on vim command line ... ) Alternatively, 'Last set from' could refer to command number as it appears in the :history (commands are numbered there). But if that command was too long ago that it dropped from history, you can't see it using :history. Just my 5c Yakov
Re: :diffsplit | verbose set fdm?
Yakov Lerner wrote: On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Benji Fisher wrote: While replying to a post on the vim users' list, I noticed a slight problem. The diff commands set some options, but this is not reported with verbose set. For example :e foo.txt :set fdm=marker :diffsplit bar.txt :wincmd w back to foo.txt :verbose set fdm? foldmethod=diff :only :verbose set fdm? foldmethod=manual --Benji Fisher Since you entered the built-in command which changed the 'fdm' option at the keyboard, there is no script or modeline to 'verbose'ly report. Or is the file actually not manually folded at the last step? I don't understand in what way the actual behaviour differs from the expected behaviour. The copy of command itself could be remembered to be printed later by 'verbose set fdm?', like this: Last set from interactive, 33 commands ago ':diffsplit bar.txt' Or the first 80 chars of the command, in case it was too long (single vim command half million characters long was discussed recently on the list ... although it was not typed interactively on vim command line ... ) Alternatively, 'Last set from' could refer to command number as it appears in the :history (commands are numbered there). But if that command was too long ago that it dropped from history, you can't see it using :history. Just my 5c Yakov Maybe; but IMHO that would be a request for enhancement, not a bug. I thought Benji meant that Vim was not behaving as advertised. Best regards, Tony.
Re: :diffsplit | verbose set fdm?
On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Yakov Lerner wrote: On 10/13/06, A.J.Mechelynck [EMAIL PROTECTED] wrote: Benji Fisher wrote: While replying to a post on the vim users' list, I noticed a slight problem. The diff commands set some options, but this is not reported with verbose set. For example :e foo.txt :set fdm=marker :diffsplit bar.txt :wincmd w back to foo.txt :verbose set fdm? foldmethod=diff :only :verbose set fdm? foldmethod=manual --Benji Fisher Since you entered the built-in command which changed the 'fdm' option at the keyboard, there is no script or modeline to 'verbose'ly report. Or is the file actually not manually folded at the last step? I don't understand in what way the actual behaviour differs from the expected behaviour. The copy of command itself could be remembered to be printed later by 'verbose set fdm?', like this: Last set from interactive, 33 commands ago ':diffsplit bar.txt' Or the first 80 chars of the command, in case it was too long (single vim command half million characters long was discussed recently on the list ... although it was not typed interactively on vim command line ... ) Alternatively, 'Last set from' could refer to command number as it appears in the :history (commands are numbered there). But if that command was too long ago that it dropped from history, you can't see it using :history. Just my 5c Yakov Maybe; but IMHO that would be a request for enhancement, not a bug. I thought Benji meant that Vim was not behaving as advertised. Benji used word problem not word bug. Literally speaking, vim behaves per doc here because ':help set-verbose' mentions When the option was set by hand there is no Last set message. But I share Benji's judgement. When command sets option indirectly, it's always kind of surprise, and I'd prefer ':verbose set xyz' to show exactly which by-hand command did it. This would be helpful in cases of indirect option switching. Yes this is change request. But I feel it makes sense. Yakov
