From: "Andrés Martinelli" <andmarti@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] terminal spreadsheet - sc fork
Date: Tue, 4 Nov 2014 10:39:23 -0300 [thread overview]
Message-ID: <CABSTndaycTffhVGg6ETpUZ48VGw5EHCgQue_Zcp1-WnH=JMh5Q@mail.gmail.com> (raw)
In-Reply-To: <5458D341.8050206@alectenharmsel.com>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
Hello! Please feel free to modify the Makefile and open a pull request!
What you mention about return values not checked, I believe they are part
of sc, but
please specify them if you can, since there's still a lot of sc for modify.
Thanks!
Andrés M.
2014-11-04 10:23 GMT-03:00 Alec Ten Harmsel <alec@alectenharmsel.com>:
>
> On 11/02/2014 06:16 PM, Andrés Martinelli wrote:
> > Hello there!!
> > I am working on a terminal spreadsheet based on "sc", but with some
> > adds like undo/redo..
> > you can find it here:
> >
> > https://github.com/andmarti1424/scim
> >
> > Any new ideas and/or contribution is always welcome!
> > Thanks!
> >
> > --
> > Andrés M.
>
> If I can offer some constructive criticism based on my short experience
> helping Walter:
>
> * Your build process could use some work; you shouldn't be hard-coding
> variable values like LN and CC in a Makefile, these are handled by make.
> Your Makefile could be shortened by ~150 lines by relying on built-in
> rules and using some built-in make expressions to list your source files
> as well.
> * A bunch of your .c or .h files are marked as executable... why?
> * No install command. Not really a huge deal as only one important file
> is produced (src/scim), but would be nice to have
>
> If you're unfamiliar with make and have no immediate plans to switch to
> either the autotools or cmake, I would be more than willing to make some
> changes to your Makefile and open a pull request. If you would like to
> email me personally with questions about make, feel free to do that as
> well.
>
> There are a couple things I saw in the code as well:
>
> * system("echo -n 'Press enter to return.'")
> * Lot of ignored return values on functions that you should check, like
> write() and fgets()
>
> If these were in the sc code and you know about them but just haven't
> gotten to fixing them yet, no worries.
>
> Alec
>
>
--
Andrés Martinelli
[-- Attachment #2: Type: text/html, Size: 2638 bytes --]
prev parent reply other threads:[~2014-11-04 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 23:16 [gentoo-user] terminal spreadsheet - sc fork Andrés Martinelli
2014-11-03 8:57 ` Wang Xuerui
2014-11-04 11:36 ` Walter Dnes
2014-11-04 11:39 ` Andrés Martinelli
2014-11-05 1:13 ` Walter Dnes
2014-11-04 12:57 ` Alec Ten Harmsel
2014-11-05 0:47 ` Walter Dnes
2014-11-04 16:30 ` Henrique Lengler
2014-11-04 16:41 ` Andrés Martinelli
2014-11-04 13:23 ` Alec Ten Harmsel
2014-11-04 13:39 ` Andrés Martinelli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABSTndaycTffhVGg6ETpUZ48VGw5EHCgQue_Zcp1-WnH=JMh5Q@mail.gmail.com' \
--to=andmarti@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox