Martin Vermeer wrote:
On Sun, Apr 06, 2008 at 04:26:23AM +0200, Pavel Sanda wrote:
I think this is to make sure we're dissolving the right kind of inset
(e.g., a charstyle), but I'm not absolutely positive.
yes and my questions are
- why is this needed - this lfun can be called withou
On Sun, Apr 06, 2008 at 04:26:23AM +0200, Pavel Sanda wrote:
> > I think this is to make sure we're dissolving the right kind of inset
> > (e.g., a charstyle), but I'm not absolutely positive.
>
> yes and my questions are
> - why is this needed - this lfun can be called without any argument.
> -
> I think this is to make sure we're dissolving the right kind of inset
> (e.g., a charstyle), but I'm not absolutely positive.
yes and my questions are
- why is this needed - this lfun can be called without any argument.
- why it is limited to FLEX_CODE.
pavel
Pavel Sanda wrote:
b) can somebody help me to understand what is the optional parameter of
dissolve inset
for? i see the parameter is used only in getStatus:
case LFUN_INSET_DISSOLVE:
if (!cmd.argument().empty()) {
> b) can somebody help me to understand what is the optional parameter of
> dissolve inset
>for? i see the parameter is used only in getStatus:
>
> case LFUN_INSET_DISSOLVE:
>if (!cmd.argument().empty()) {
>
