linux raw packets (c)

[md]

Justin_ wrote:

So I guess you don't know the includes it needs? And here's another question for you. In windows ctrl-c = copy. Is there a keyboard short cut like this for linux? I'm guessing no, because it depends on the current thread that's running.

What editor are you using? There is almost certainly copy functionality; though the keys might be different.

[Justin_]

emacs, but I was really asking for a universal copy shortcut, for shell and everything. I didn't think there was one. When I think of linux I think of the most user unfriendly environment imaginable. The one good thing about commercial software is it adheres to standards.

[wtd]

So, why use emacs? Just edit in something like gedit and then use the shell to compile. You can have your cake and eat it too.

[Justin_]

I don't understand what I'd be gaining if I edited in Gedit but thanks anyway.

[wtd]

A decent GUI environment? The keyboard shortcuts you're used to?

[Justin_]

What keyboard shortcuts? I specifically asked if there were any. Wow.

[wtd]

Gedit is a GUI text editor. It's standard issue with recent versions of the Gnome desktop environment, and from screenshots, it appears you're using that.

Remember, the GUI and the command-line are not entirely separate. They both deal with the same filesystem.

[Justin_]

I know this. I'm sorry you're confused what my question actually is.

My questions that remain unanswered are:

What headers do I need to compile that raw socket code example in linux?

And on the side:

In linux, are their keyboard shortcuts for copy and paste like ctrl-c in windows?

[wtd]

There weren't include directives in this code you downloaded? Because before it seemed you were asking about which libraries you needed to link against, and now it seems you're asking about headers. These are very different things.

[md]

Justin_ wrote:

In linux, are their keyboard shortcuts for copy and paste like ctrl-c in windows?

As I tried to point out it depends on what program you are using. If your using something like gedit then the keys are crtl-c and crtl-v just like windows. If your using something else try reading the man pages or using google.

[Justin_]

That sucks Cornflake. Truly, I mean imagine having to learn new hotkeys for every single program just because people can't devise one standard.

Well before I phrased the question "what includes do I need" and I figured that was explicit enough considering include is the keyword for including headers.

For example:

#include <iostream>

what do I include for this program in linux?

[md]

Justin_ wrote:

That sucks Cornflake. Truly, I mean imagine having to learn new hotkeys for every single program just because people can't devise one standard.

Well before I phrased the question "what includes do I need" and I figured that was explicit enough considering include is the keyword for including headers.

For example:

#include <iostream>

what do I include for this program in linux?

No, it makes sense when you look at the differences between linux and windows. On linux there are many many character/console based programs, and in those programs ctrl+whatever is almost always an important escape sequence that can't be over-written, or is better overwritten with something more inline with what hte original escape sequence is supposed to do. For instance ctrl-c causes most programs to exit. Making it instead copy text would just confuse habitual linux users. When you use graphical tools like gedit or any of the other X based editors copy and paste are almost always the same as their windows counter-parts as escape sequences aren't as integral in a graphical enviroment.

If you don't want to take the time to learn the commands for emacs then use something else. Complaining because you are lazy seems pretty poor to me.

As for the include I would imagine that whatever tutorials you were using would tell you. Perhaps reading them instead of just swiping the code might be a good idea. 'Course it's really not that hard to guess it's something like sockets.h

[Justin_]

lol, you win, i'll stop posting here. It's getting to be a bad experience for me with all the bull shit.