On Tue, 17 Jan 2012 at 19:01:52 +0100, Rodolfo kix Garcia wrote:
>
> Ok, ok, is wrong, but... who make patches, make mistakes :-)
Right, but that particular bit was clearly written directly in
the email and everyone can filter this kind of irrelevant lapse.
The important thing is to discuss.
You
On 17/01/12 18:45, Carlos R. Mafra wrote:
> On Mon, 16 Jan 2012 at 17:48:41 +, SJS wrote:
>>
>> And stylistically, I assert that it's clearer to write
>>
>>buffer[DOCK_NAME_LEN - 1]
>>
>> than
>>
>>buffer[DOCK_NAME_LEN -1]
>>
>> ...but that's just a pet peeve of mine, since I read "-1"
On Mon, 16 Jan 2012 at 17:48:41 +, SJS wrote:
>
> And stylistically, I assert that it's clearer to write
>
>buffer[DOCK_NAME_LEN - 1]
>
> than
>
>buffer[DOCK_NAME_LEN -1]
>
> ...but that's just a pet peeve of mine, since I read "-1" as being "one less
> than zero", so "-1" might as
begin quoting Rodolfo kix Garcia as of Mon, Jan 16, 2012 at 09:04:45AM +0100:
> On 16/01/12 08:31, Rodolfo kix Garcia wrote:
[chop]
> > snprintf(buffer, DOCK_NAME_LEN -1, _("Type the name for workspace %i:"),
> > wks_no + 1);
>
> buffer[DOCK_NAME_LEN -1] = '/0';
>
> Can help too.
Surely \0 is
On Mon, 16 Jan 2012 12:51:50 +, Carlos R. Mafra wrote:
On Mon, 16 Jan 2012 at 8:31:33 +0100, Rodolfo kix Garcia wrote:
>
[snip]
> + char buffer[128];
I don't like this things, I prefer "char buffer[DOCK_NAME_LEN]" and
set
DOCK_NAME_LEN in dock.h Probably we should find i
On Mon, 16 Jan 2012 at 8:31:33 +0100, Rodolfo kix Garcia wrote:
> >
> [snip]
> > + char buffer[128];
>
>
> I don't like this things, I prefer "char buffer[DOCK_NAME_LEN]" and set
> DOCK_NAME_LEN in dock.h Probably we should find if this length is used
> in other places in the
On 16/01/12 08:31, Rodolfo kix Garcia wrote:
> On 16/01/12 06:56, Carlos R. Mafra wrote:
>
>> On Tue, 10 Jan 2012 at 0:34:53 +0100, Rodolfo kix Garcia wrote:
>>>
>>> Why we can change the name using right click on the Clip. Why? because
>>> the clip is using the functions of WINGs. Can we change
On 16/01/12 06:56, Carlos R. Mafra wrote:
> On Tue, 10 Jan 2012 at 0:34:53 +0100, Rodolfo kix Garcia wrote:
>>
>> Why we can change the name using right click on the Clip. Why? because
>> the clip is using the functions of WINGs. Can we change the menu
>> functions to WINGs?... probably yes, but
On Tue, 10 Jan 2012 at 0:34:53 +0100, Rodolfo kix Garcia wrote:
>
> Why we can change the name using right click on the Clip. Why? because
> the clip is using the functions of WINGs. Can we change the menu
> functions to WINGs?... probably yes, but I don't know. Probably the full
> code of menu s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/12 20:45, Rodolfo kix Garcia wrote:
> On 09/01/12 19:12, Andreas Metzler wrote:
>> On 2012-01-08 Rodolfo kix Garcia wrote:
>>
>>> I can do it. I can set the Workspace name to "ö" o "ñ" using the
>>> dialog box.
>> Hello,
>> I have tried usin
On 09/01/12 19:12, Andreas Metzler wrote:
On 2012-01-08 Rodolfo kix Garcia wrote:
I can do it. I can set the Workspace name to "ö" o "ñ" using the dialog box.
Hello,
I have tried using the Method listed in the FAQ:
Application-Menu -> WorkSpace -> Workspaces ->
Ctrl-Leftklick on the to
11 matches
Mail list logo